Running Workflow from App 504 Timeout

When triggering a workflow from an application that takes longer than 30 seconds for the response this causes a 504 error. There are cases I expect this to happen and I'm wondering if there is a setting somewhere to tune this.

1 Like

@notthatbreezy thanks for asking -- I've seen one other instance of a customer running into a similar error and scenario. In that case, the hypothesis was the issue had something to do with their own internal vpn configuration.

The recommendation to work around this issue was that your workflow should save its return value to a Retool DB table, and then you can poll for the results in your app with a query to that RetoolDB resource. Hope this helps you or others in a similar situation!