For common issues that apply to all connectors — authentication failures, syncs stuck or not progressing, no documents indexed, stale permissions — see Troubleshooting - Enterprise Search Connectors.
Symptoms: The connector saves, but the first sync fails immediately with a permission error, or completes with zero items.
Possible causes:
The Help Article REST API domain was granted to the integration security group, but Activate Pending Security Policy Changes was never run, so the grant is still pending.
The domain was not granted at all, or was granted to a different security group than the one containing the Integration System User.
The API client was registered without the Help functional area scope.
OAuth 2.0 Clients Enabled is not selected under Edit Tenant Setup - Security, so no API client can reach the Workday API for the tenant.
Resolution:
Run Activate Pending Security Policy Changes in Workday, confirm the changes, then trigger a sync from Enterprise Search → Workday → Status. This resolves the majority of cases.
Open the Integration System Security Group and confirm Help Article REST API is granted with both Get (Integration Permissions) and View Only (Report/Task Permissions), and that the group lists your Integration System User.
Run the View API Clients report, open your client, and confirm Help appears in its functional area scope. If it does not, re-register the client with the Help scope and generate a new refresh token — then update both values in Simpplr.
Run Edit Tenant Setup - Security and confirm OAuth 2.0 Clients Enabled is selected.
Symptoms: The connector synced successfully for a period, then began failing with an authentication error.
Possible causes:
The API client was registered without Non-Expiring Refresh Tokens, so the refresh token has expired.
The refresh token was regenerated or deleted in Workday, invalidating the value stored in Simpplr.
The client secret was rotated in Workday.
The Integration System User was deactivated, or its Session Timeout Minutes was changed from 0.
Resolution:
Run View API Clients, open your client, and confirm Non-Expiring Refresh Tokens is selected. If it is not, select it.
Generate a new refresh token for the Integration System User through API Client → Manage Refresh Tokens for Integrations, then update the Refresh token field in the connector configuration in Simpplr.
If the client secret was rotated, update the Client secret field in Simpplr as well.
Confirm the Integration System User is active and that its session timeout is still 0.
Symptoms: The sync reports Success, but the indexed count is a fraction of the articles your HR team can see in Workday Help.
Possible causes:
Expected behaviour. Only article versions whose status is Published and whose audience includes Public are indexed. Draft and archived versions and audience-restricted articles are excluded by design.
Articles not updated in the last 2 years are excluded by the fixed article-age window.
Resolution:
In Workday, check how many article versions are Published and carry the Public audience. That number, narrowed to articles updated in the last 2 years, is the expected indexed count.
To bring a restricted article into search, have your HR team add the Public audience to it in Workday — and only where the article is genuinely appropriate for all employees. It will be indexed at the next full sync.
To bring an older article into scope, edit it in Workday. That refreshes its last-updated date.
Symptoms: Saving the connector configuration fails with a message about the Workday host.
Cause: The Workday host field accepts only an HTTPS URL with no path. A value copied straight from the Token Endpoint URL still contains /ccx/oauth2/{tenant}/token and is rejected, as is a host entered without https://.
Resolution: Enter only the scheme and hostname in Workday host — for example https://wd2-impl-services1.workday.com — and put the tenant segment from the token endpoint in Tenant name. See Setup - Workday, step 8.
Common questions about sync frequency, deletions, audience filters, and throttling are answered in Troubleshooting - Enterprise Search Connectors. Security, privacy, and data questions are answered in Data & Security - Enterprise Search Connectors.
Q. Which Workday Help articles are indexed?
Only article versions whose status is Published and whose audience includes Public. Draft and archived versions are excluded, as are articles targeted only at a restricted audience. See Content, Sync & Limitations - Workday.
Q. How long until a new or updated article appears in search?
Up to 24 hours. Content changes are picked up at the next daily full sync; there is no incremental sync for this connector in this release.
Q. Are files attached to a Workday Help article indexed?
No. Only the article's own title and body text are indexed. An attached PDF or document is not searchable through this connector.
Q. Why does the connector need an unconstrained integration security group?
Workday requires it for an integration user to call the Help Article service for the tenant rather than for one worker's own data, and offers no narrower grant that returns only Public-audience articles. The connector discards everything outside the Public audience before indexing. See Permissions & Security - Workday.
Page | What it covers |
|---|---|
What the connector indexes and capabilities at a glance | |
Auth mechanism, credential scope, permission design, supported editions | |
Prerequisites and step-by-step configuration | |
Fields synced per content type, sync schedules, data freshness, limitations in detail |