# Workday aggregation Issue

**URL:** <https://developer.sailpoint.com/discuss/t/workday-aggregation-issue/202111>\
**Category:** SHF Discussion and Questions\
**Tags:** sailpoint-identity-security\
**Created:** [April 9, 2026, 2:00pm UTC](https://developer.sailpoint.com/discuss/t/workday-aggregation-issue/202111 "2026-04-09T14:00:47Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jadhikary](https://avatars.discourse-cdn.com/v4/letter/j/9dc877/32.png) [@Jadhikary](https://developer.sailpoint.com/discuss/u/Jadhikary)\
**Post date:** [April 9, 2026, 2:00pm UTC](https://developer.sailpoint.com/discuss/t/workday-aggregation-issue/202111/1 "2026-04-09T14:00:47Z")

</div>

> ‼ Please be sure you’ve read the [docs](https://developer.sailpoint.com/idn/docs/) and [API specs](https://developer.sailpoint.com/idn/api/getting-started) before asking for help. Also, please be sure you’ve [searched](https://developer.sailpoint.com/discuss/search?expanded=true) the forum for your answer before you create a new topic.

## Please consider addressing the following when creating your topic:

We have a workday connector and for the last few days we are seeing partial error while performing the aggregation.

Whenever it is running, it aggregates around 5k users and fails but in total we have around 7k users from Workday.

Error:

**S22 permission error.**

Please let me know if anyone has faced this issue.

---

<div class="post-metadata">

**Author:** ![baoussounda](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/baoussounda/32/13095_2.png) [@baoussounda](https://developer.sailpoint.com/discuss/u/baoussounda)\
**Post date:** [April 9, 2026, 2:04pm UTC](https://developer.sailpoint.com/discuss/t/workday-aggregation-issue/202111/2 "2026-04-09T14:04:54Z")

</div>

Hi @Jadhikary

This error is already mentionned and reported by Sailpoint Here

[Notice: Workday S22 Error — Impact, Root Cause, and Resolution - Announcements / Product News - SailPoint Developer Community](https://developer.sailpoint.com/discuss/t/notice-workday-s22-error-impact-root-cause-and-resolution/199142)

And they explain how to resolve it there.

---

<div class="post-metadata">

**Author:** ![utkirjonkamiljanov](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/utkirjonkamiljanov/32/36695_2.png) [@utkirjonkamiljanov](https://developer.sailpoint.com/discuss/u/utkirjonkamiljanov)\
**Post date:** [April 9, 2026, 3:34pm UTC](https://developer.sailpoint.com/discuss/t/workday-aggregation-issue/202111/3 "2026-04-09T15:34:39Z")

</div>

Open this URL:

> [@Notice: Workday S22 Error — Impact, Root Cause, and Resolution](https://developer.sailpoint.com/discuss/t/notice-workday-s22-error-impact-root-cause-and-resolution/199142):
>
> Overview Recently, multiple Workday sources across Sandbox and Production environments have been impacted by the Workday S22 error. The S22 error code in Workday indicates a “Permission Denied” response. This typically occurs during integration attempts (API or custom integrations) when the user account, API client, or security group lacks the necessary permissions or scopes required to perform a specific action. This issue particularly affects Workday sources where either of the following are…

There is one step details to assign some permission in Workday to the service account that you are using. Send this information to your Workday team and ask them to add those 2 permission. Once it is added, it will get fixed.

I have also faced this problem and got it fixed like this.

Thanks

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [June 8, 2026, 3:34pm UTC](https://developer.sailpoint.com/discuss/t/workday-aggregation-issue/202111/4 "2026-06-08T15:34:56Z")

</div>

Closed on June 8, 2026, 3:34pm UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
