Context:
We are seeing intermittent 504 Gateway Timeout errors in our Architect flow immediately following the weekly schedule publish at 17:00 CST. The flow handles shift swap approvals and calls the WFM API. It works fine manually but fails during the high-load publish window.
Question:
Could someone explain the best practice for handling API rate limits or timeouts in Architect flows when triggered by bulk WFM updates? Should we implement retry logic within the flow or adjust the publish timing?