How come this setting causes the script engine to reject dynamic variables when agent counts spike?
We are seeing intermittent failures in our Architect flows during the Chicago morning rush (America/Chicago). When agents process shift swaps, the WFM module updates the queue capacity. Simultaneously, the script attempts to inject the agent’s current shift end time via a data action. The script fails to render the prompt, returning a 500 Internal Server Error on the /api/v2/architect/flows endpoint. This happens specifically when the queue has over 200 active agents. We are on Genesys Cloud 2024.4. Is there a concurrency limit on script variable resolution tied to WFM updates?