SAP Fieldglass 2511-SP1 Breaking Change for Fieldglass connector - 500 Internal Server Errors when Aggregating Accounts

[mcheek (Mark Cheek)]

I’m reaching out here to see if there is anyone using the SAP Fieldglass connector who has recently started experiencing errors after the release of 2511-SP1 from Fieldglass on 14 November (US tenants)

We started seeing these aggregation errors starting on the first aggregation of 15 November and every aggregation since

The FG connector first attempts to find all account attributes from a FG report specified in the connectorAttributes (one for user, one for worker, one for single worker). If the connector is unable to find all the attributes in the account schema from the respective report, it falls back to calling the Fieldglass SCIM API to get those attributes

From the ccg log

"message":"No data found for userName 'USERNAMEREDACTED' in user report. Hence, report specific attributes can not be fetched. Also, can not determine its correct status. Falling back on SCIM status."

A couple of lines later, we see the following message

"message":"Response received for URL https://redacted.us.fieldglass.cloud.sap/api/v1/Users?startIndex=751&count=50 in 1152 millis, status code 500, Response size 107 bytes."

I was able to reproduce this error in Postman

You can understand why this is happening when you reduce the startIndex to 700

My conclusion is that the SAP Fieldglass connector is incorrectly paging results in the Fieldglass SCIM API - this appears to be a bug. I’ve opened a support case, but I was going to see if anyone else is experiencing it?

[Chaithu9110 (CHAITHANYA M)]

same here in previously it was working fine

[mcheek (Mark Cheek)]

That’s interesting- I’m not seeing that particular error happen in my aggregation

[hjoe-1 (Joe Hill)]

We are seeing the same error @mcheek. We also submitted a ticket with SailPoint and SAP.

[mcheek (Mark Cheek)]

Latest from support - it appears that it was a breaking change they’re working on

The SAP Fieldglass issue is affecting other customers as well due to a release on the SAP side. Due to this release, we’ve discovered the SAP API endpoint /api/v1/Users?startIndex=0&count=50 is experiencing issues which affects aggregations. Previously, when the startIndex exceeded the total number of available records, the API would return an empty response as expected. However, for the last few days, we are consistently receiving a 500 Internal Server Error instead.
Our connector engineering team is working with SAP in an effort to expedite a resolution. I’ll reach back out as I receive new information. Thank you for your patience.

[hjoe-1 (Joe Hill)]

We had a call with SAP last week and they fixed this issue with the last patch that went through on last Saturday. Hopefully everyone has this issue fixed now.

[Bobbo_za (Robert Bouw)]

Hi All, Different error but is anyone else having an issue with the Fieldglass connector currently? We’re currently getting: Error Received:

Cannot invoke “openconnector.ConnectorServices.getFeatureFlagValue(String, boolean)” because the return value of “openconnector.AbstractConnector.getConnectorServices()” is null}