No idea why this is happening, the Agent Scripting API is returning a 409 Conflict when attempting to update existing script resources via our AppFoundry integration. The environment is a multi-tenant setup where each customer organization has its own isolated instance, and the integration handles script synchronization from our central platform.
The specific endpoint failing is PUT /api/v2/scripts/{scriptId}. The error response includes the message: “Resource conflict: The script version provided in the request does not match the current server version.” This occurs even when the If-Match header contains the exact ETag value retrieved from the initial GET request within the same transaction block.
We have verified that no other processes are modifying the script between the read and write operations. The integration uses OAuth 2.0 client credentials flow with the script:read and script:write scopes. The issue appears consistently when the script content exceeds 15KB, suggesting a potential payload size limitation or versioning quirk in the API layer.
Has anyone encountered similar versioning conflicts with the Agent Scripting API in a high-throughput environment? We are considering implementing exponential backoff with version retries, but this seems like a fundamental API behavior issue rather than a race condition.
Environment details:
- Genesys Cloud API Version: v2
- AppFoundry Integration: Multi-tenant, OAuth 2.0 client credentials
- Script Content: JSON format, varying sizes from 5KB to 25KB
- Error Frequency: 100% reproducible when payload > 15KB
The Agent Scripting API documentation mentions versioning requirements but does not specify behavior for large payload updates. Any insights into the underlying conflict resolution logic would be appreciated.