quick question about a weird issue we are seeing. trying to integrate our weekly schedule publish logic with an architect flow. basically want the IVR to check if an agent is actually scheduled before routing. using the wfm schedule api in a data action. getting a 502 bad gateway error sporadically. happens mostly on tuesdays when we push the new roster. the api call works fine in postman but fails in the flow. suspecting it might be a timeout issue since the schedule object is huge for our 500+ agents. is there a known limit on response size for data actions? also noticed the error message is empty. just 502. running on us-east-1. anyone else hit this when pulling schedule data from wfm into architect? trying to avoid hardcoding availability. would love to know if this is a platform bug or just bad config on our end. thanks in advance!