3rd Party: Ramp connections are failing with "403 Forbidden" error

We have resolved this incident.

We are now observing 403 Forbidden errors on the spend_program and limits endpoints, in addition to the previously impacted endpoints. The issue is consistent with a scope-related insufficient permissions error.

We are working on a hotfix to extend the fix to include these endpoints, handle the 403 Forbidden error, and fix the issue.

The hotfix has been deployed successfully. We are monitoring the connector syncs now.

A hotfix has been created and is currently being deployed

Multiple endpoints (including Bill, Purchase Order, Business Entity, Vendor, and Merchant) require specific permissions to sync. A recent third-party change caused missing-permission errors to return a 403 Forbidden instead of a 400 Bad Request. This change bypassed the existing skip logic, resulting in connection sync failures.

We are working on a hotfix to handle the 403 Forbidden error to fix the issue.

The issue has been identified and we are working to resolve it.