Extend Orchestration WQL Call Returns 403 Permission Denied S22 As The ISU
The error [StepException] Failed to retrieve Paged API response, status code: 403, error: {"error":"permission denied","code":"S22","severity":"Critical"} @[<OrchestrationName>._orchestration.<StepName>.<StepName>]
What does "Extend Orchestration WQL Call Returns 403 Permission Denied S22 As The ISU" mean in Workday Extend?
The orchestration got a token for its ISU, but Workday refused the WQL query. S22 is Permission Denied: the user's security policies do not allow the request. For WQL the usual missing piece is the Workday Query Language domain itself, which is separate from the domains that secure the data being queried.
Quick fix
Add the Workday Query Language domain (System) to the ISU's security group, activate pending security policy changes, and rerun.
Permanent fix
Put the Workday Query Language domain in every Extend orchestration ISU's security group that runs WQL, alongside the data source domains, and apply it in each tenant before the first run.
Troubleshooting
- In the developer site log, find the 403 entry for the WQL path and confirm wd_username is the ISU and wd_api_client_id is the expected client. If both are right, the refusal is the ISU's security.
- Add the Workday Query Language domain (System functional area) to the ISU's integration system security group. It is a domain, so look it up as a domain security policy, not a securable item. In the case behind this entry, this grant alone cleared the error; API client scopes did not need to change.
- Confirm the group also has access to the domain that secures the data source, and to the domains behind any reference fields the query returns, such as worker data.
- Run Activate Pending Security Policy Changes and rerun.
- A query that returns no rows can succeed in another tenant without these grants, so a clean run there does not prove the security is complete.
- If it still fails, open a Workday case with the request id from the log.
Was this helpful?