No idea why this is happening, our AppFoundry integration is consistently failing to push updated edge configurations to our Bring Your Own Cloud (BYOC) environment. We are attempting to programmatically update the custom header mappings for specific edge clusters via the PATCH /api/v2/billing/edges/{edgeId} endpoint, but the platform returns a 409 Conflict error immediately after the request is initiated.
The integration runs on a Node.js 18.x backend using the Genesys Cloud Node SDK version 3.42.0. The OAuth token is valid and has the edges:write scope. We have verified that the payload matches the schema defined in the Swagger documentation exactly, including the required clusterId and region fields. The conflict appears to be related to the customHeaders object, specifically when we attempt to add a new header mapping for secure cookie transmission.
The error response body provides limited detail:
{
“code”: “conflict”,
“message”: “The requested update conflicts with an existing resource state or ongoing operation.”,
“details”: “Edge configuration lock held by another process or inconsistent state detected.”
}
We are operating in the mypurecloud.com environment with a multi-org setup. The target edge cluster is located in us-east-1 and is currently marked as active in the UI. There are no other automated processes running against this specific edge ID during the update window. We have implemented a retry logic with exponential backoff, but the 409 persists regardless of the delay interval.
Is there a specific locking mechanism or state requirement for BYOC edge configurations that is not documented? We suspect the platform might be holding a stale lock due to a previous failed async operation, but we have no way to clear this state via the API. Any insights into debugging this specific conflict scenario would be appreciated.