Skip to content
Managing Extended c...
 
Notifications
Clear all

Managing Extended callin.io Workflows: Strategies for Browser Timeouts with API GET Requests

3 Posts
3 Users
0 Reactions
6 Views
elvismdev
(@elvismdev)
Posts: 1
New Member
Topic starter
 

Describe the problem/error/question

When initiating a lengthy workflow through an API GET request in a browser, the request encounters a timeout after approximately 2 minutes. This occurs even though the workflow continues to run successfully and finishes in about 8 minutes, as confirmed by the callin.io execution list. The objective is to obtain a JSON response from the final “Respond to Webhook” node, but the premature browser timeout prevents this, disrupting the expected data retrieval. The core question is how to manage or configure settings to accommodate these situations where the browser’s timeout limit is surpassed by the workflow's execution time.

What is the error message (if any)?

Error code 524

Share the output returned by the last node

Just a JSON response like this format after processing the entire workflow, involves between 2 to 5 API calls + data processing trough 2 AI models:

[
  {
    "appended_bullet": [
      "In enim justo rhoncus ut",
      "Vivamus aliquet elit ac nisl",
      "Donec mi odio faucibus at",
      "Ut non enim eleifend felis",
      "Aenean leo ligula porttitor eu"
    ]
  }
]

Information on your callin.io setup

  • callin.io version: 1.36.1
  • Database (default: SQLite):
  • callin.io EXECUTIONS_PROCESS setting (default: own, main):
  • Running callin.io via (Docker, npm, callin.io cloud, desktop app): Docker
  • Operating system: Ubuntu
 
Posted : 21/04/2024 1:02 am
barn4k
(@barn4k)
Posts: 6
Active Member
 

Hello

I believe the most suitable approach is to utilize an alternative method for receiving the response, such as email.

Most browsers maintain a session for approximately 60-120 seconds. If no response is received within this timeframe, the session is terminated. To my understanding, callin.io cannot send keep-alive signals until the response is prepared for transmission (please correct me if I'm mistaken).

Therefore, from the browser's perspective, an 8-minute response will invariably be considered timed out.

 
Posted : 21/04/2024 8:20 pm
system
(@system)
Posts: 332
Reputable Member
 

This thread was automatically closed 90 days following the last response. New responses are no longer permitted.

 
Posted : 20/07/2024 8:21 pm
Share: