Hey everyone, I’ve run into a really strange issue with our custom Data Action that syncs shift preferences. The HTTP request to the external WFM tool fails with a 504 Gateway Timeout exactly during the Monday 06:00 CT publish window.
Error: Request Timeout
Code: 504
Endpoint: /api/v2/wfm/scheduling/schedules
The flow works fine on Tuesdays. Is there a known resource contention issue with Architect during the publish job? Need to ensure agent swap validations don’t break.
TL;DR: Bypass the timeout.
I usually solve this by offloading the sync to a background worker triggered by the publish event, rather than blocking the Architect flow with a synchronous HTTP call. The 504 is likely Architect’s hard limit on action execution time during peak scheduling windows.
The problem here is Architect’s hard timeout limit during the Monday publish surge. Do not increase the timeout value as it will just delay the inevitable 504. Offload the sync to a background worker as suggested above.