Architect Flow: 500 Internal Server Error on Custom API Action within Multi-Org AppFoundry Integration

Is it possible to invoke a custom API action from within an Architect flow using an OAuth token generated by an AppFoundry integration that spans multiple organizations? We are building a premium integration for a client in the Pacific timezone and encountering a 500 Internal Server Error when the flow executes a POST request to our external service via the Custom API action. The error payload returned by Genesys Cloud indicates a timeout, yet our backend logs show the request never arrived. We have verified that the OAuth token used in the flow context has the necessary api:read and api:write permissions, and the integration is correctly scoped to the target organization. The flow is designed to trigger upon a specific IVR menu selection, and while standard actions like Set Variable and Play Prompt function without issue, the external call fails consistently. We are using the latest version of the Architect flow designer and have confirmed that the external endpoint is accessible from the Genesys Cloud network via their IP allow-list. Has anyone experienced similar latency or connection drops when using custom API actions in high-volume IVR flows, and are there specific timeout configurations or retry policies we should implement within the flow to mitigate these failures?