What is the correct way to handle service now rest api timeouts from genesys cloud architect

How should I properly to handle service now rest api timeouts from genesys cloud architect when triggering data actions via conversation events? the flow hangs on the http request step, returning a generic gateway timeout after 30s. the service now instance is responsive, but the payload includes large interaction history arrays. is there a documented way to configure retry logic or chunk the payload within the architect flow to avoid dropping the call context while waiting for the ticket creation confirmation?