Does anyone know how to properly configure the timeout settings for a custom Architect script node that triggers during approved shift swaps? We are seeing a spike in 504 Gateway Timeout errors specifically when agents execute shifts via the WFM self-service portal in Genesys Cloud CX v2024.04. The issue seems to correlate with our weekly schedule publishing window in America/Chicago timezone, where concurrent requests hit the POST /api/v2/wfm/schedules/agent endpoint.
The script is designed to validate agent capacity before finalizing the swap, but the integration with our internal capacity calculator via AppFoundry is timing out under load. We have increased the node timeout to 30s in Architect, but the error persists. The logs show the initial request succeeds, but the callback to update the schedule adherence status fails.
We are using the Python 3.9 SDK for the backend validation. Is there a recommended pattern for handling these long-running WFM operations without triggering the gateway timeout? We need to ensure shift swaps are processed reliably without dropping the adherence data.