OpenWebUI timeout issue after 60s when using with n8n pipe

Questions
4

Hi @hussein_Abusetta

I have a method that works around this issue. This approach ensures that you can manage long-running workflows effectively by leveraging polling and execution status checks.

Here’s a quick summary:

  1. Call the webhook and immediately respond with the execution ID.
  2. Store the execution ID in your Pip function.
  3. Poll the n8n API every 5 seconds to check the execution status using the endpoint: https://www.n8n/api/v1/{execution_id}?includeData=false.
  4. Once the execution status is "finished": true, fetch the full execution data using: https://www.n8n/api/v1/{execution_id}?includeData=true.
  5. Extract the data from the last node, which you can easily identify if you name it “lastNode”.

This way, you can handle long-running tasks without backend timeout issues.

Hope this helps !

1 Like