Context:
Our AppFoundry integration injects dynamic data into Architect flows via the /api/v2/analytics/icapd:real-time-query endpoint. The payload updates custom disposition codes based on real-time CRM status. During peak load in the Pacific timezone, the scripting engine returns a 409 Conflict with reason: CONCURRENT_MODIFICATION. The flow expects a sequential update, but the race condition persists despite retry logic.
Question:
Is there a specific locking mechanism or idempotency key required for the Agent Scripting API to prevent these concurrent modification errors? We are currently hitting rate limits trying to resolve this.