This incident has been resolved. We have observed that instance rates are returning to normal levels, and affected connections are syncing successfully.
Incident Summary Description: We identified an issue with the Workramp connections, which resulted in syncs failing due to unexpected API behaviour (required fields returned as null).
Timeline: This issue began on 2025-11-25 at 22:30 UTC and was resolved on 2025-11-26 at 14:00 UTC.
Cause: The source changed the extract path and response format for several tables, causing mismatches with our existing code.
Resolution: We updated our code to align with the new source changes and deployed the fix for the affected connections. Once we receive confirmation from the source support team, we will officially implement the change.
Posted Nov 26, 2025 - 17:29 UTC
Monitoring
A fix has been implemented and we are monitoring the results.
Posted Nov 26, 2025 - 14:01 UTC
Update
After further investigation, we found that the third party has updated the extract path in API endpoints, which is causing the failure. This issue is affecting guide_assignment, path_assignment and certification_award endpoints as well.
We are making a code change on our side to fix this issue for the affected connections. We will release it for all the accounts/connections once we get confirmation from the third party.
Posted Nov 26, 2025 - 09:03 UTC
Update
Multiple Workramp connections are failing during sync due to unexpected API behaviour on the source side. Required attributes are being returned as null in the impacted endpoints (v1/paths, v1/guides, and v1/certifications). Since these attributes are mandatory for processing records, the null values are causing the sync pipeline to fail.
We have reached out to the third party team to get this issue resolved. In the meantime, to avoid further breakages, we will temporarily stop syncing these impacted APIs for affected customers until the third party fixes the issue.
Posted Nov 26, 2025 - 05:34 UTC
Identified
The issue has been identified and we are working to resolve it.
Posted Nov 26, 2025 - 05:30 UTC
This incident affected: Human Resources connectors (WorkRamp).