Workiva Connector Suddenly Fails to Aggregate Entitlements — No Configuration Changes Made

I’m running into an issue with the Workiva connector where entitlement aggregation is failing, while account aggregation continues to work without errors. This setup was working fine until a few days ago, and no changes have been made to the default configuration.

Exception during aggregation of Object Type group on Application Wdesk [source]. Reason: java.lang.RuntimeException: An error occurred while aggregating Application Wdesk [source] [ConnectorError] {ExceptionType=openconnector.InvalidRequestException, LocalizedMessage=[ InvalidRequestException ] [ Possible suggestions ] Please check if provided payload has valid attributes [ Error details ] Error while performing operation : Account Aggregation Error code : 400 {“schemas”:[“urn:ietf:params:scim:api:messages:2.0:Error”],“status”:“400”,“scimType”:“invalidValue”,“detail”:“Bad Request”}}

It looks like the connector is sending an invalid or malformed payload during entitlement aggregation, possibly missing required attributes or using incorrect formats. Since no configuration changes were made, I’m wondering if something changed.

Has anyone else experienced this recently? Any suggestions on how to troubleshoot or resolve this?

Thanks in advance!

1 Like

Is it working today? I believe Workiva tenants exist in AWS and from what I can see it is a SaaS connector.

Double check whether this issue is related to AWS outage which impacts SailPoint aggregations. I would wait for a day until the outage is resolved and monitor it.

Hello Erika,

We have been experiencing the same issue in a customer’s sandbox environment on a Workiva source that was previously working. No changes made - account aggregation is working, all provisioning is working, entitlement aggregation is failing with the same error. I have submitted a support ticket yesterday. Has yours been resolved?

Hi Joseph,

I created a new source and entitlement aggregation was successful on 10/21 but now I am getting the same error. The existing source in prod failed on 10/21

Hi Joseph - Did you get any updates on this as you submitted a support ticket?

Hello Erika,

No updates as of yet, other than a response yesterday that they were looking into it. I will be following up at end of day today. If I hear back I will let you know :slight_smile:

Hello Erika,

SailPoint support sent me over an API call to run to verify the accounts being returned, I will list it below. I did not run it as this is a customer’s environment and I do not have the API token to run the call. I did however login to their ISC environment and the entitlement aggregation is now working. This is the first successful entitlement aggregation for the past two weeks. No changes were made that I am aware of by the customer or my team in their environment. I would like to know the issue that was failing the entitlement aggregation, but looks like it is now working with no changes. Is yours still failing or is it unexpectedly working as well?

API call: https:///s/scim//Groups?startIndex=1&count=50

Mine was failing in account aggregation and entitlement aggregation was working fine. Account aggregation is working now. There must have been some updates to the SaaS connector by SailPoint..

1 Like

Seems to be true by seeing the inconsistent behavior. I would get the confirmation from SailPoint team.

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