Sim.AI Workflow Blocks (API Block) Timing Out — Request to Increase Block Execution Timeout

[SAljajith]

When using Sim.AI Workflow Blocks, especially the API Block, the execution frequently fails due to block timeout.
This happens even when the external API or computation needs a few extra seconds.

The block stops executing and returns a failure even though the external API eventually responds.

Create a workflow in Sim.AI Studio.

Add an API Block that calls an endpoint requiring 220– 340 seconds (or more).

Run the workflow.

The block returns a timeout error before the external API responds.

Expected Behavior

Block should wait until the API response arrives within a reasonable limit.

The block timeout should be configurable, so users can increase max wait time.

[waleedlatif1]

@SAljajith for workflows that take longer than ~3 minutes, we recommend that users carry those tasks out asynchronously. In the deployment modal, you can see the code to run the workflow asynchronously, where you get a job id and can poll until the task is completed.

[SAljajith]

@waleedlatif1 Is there any alternative approach?
I already tried using the function-level API call, but the HTTP request isn’t working due to security restrictions.
Is there any other way to increase the timeout? I’m running Sim.ai through Docker.

[waleedlatif1]

If you are self-hosting, the only constraint applied is your infrastructure. In pure docker, its either the external API timing out, an OS/network-level timeout, or a reverse proxy. @SAljajith

[web-developer-ss]

@waleedlatif1 Where can we change the timeout configuration in the code?

[ARNOLDAJEE]

Hi @majiayu000,
We updated the respective code and ran the Sim AI. The timeout configuration in the API block is set to 600000, but I am still facing a timeout issue.
Error: The operation timed out

[majiayu000]

I will test it later @ARNOLDAJEE !

[ARNOLDAJEE]

Sure let me know once you've tested it # @majiayu000

[web-developer-ss]

@majiayu000 We have also updated the code, but the same issue still occurs.

[majiayu000]

Hi @ARNOLDAJEE @web-developer-ss,

I've done comprehensive testing on my PR #2519 and confirmed that the timeout functionality works correctly:

Test Results:

• ✅ 16 unit tests passed (timeout parameter parsing, AbortSignal integration)
• ✅ Real HTTP tests passed using httpbin.org (verified actual timeout behavior)
• ✅ Timeout correctly triggers when response time > configured timeout
• ✅ Requests complete successfully when response time < configured timeout

Important Question: Are you using the code from my PR branch?

My PR #2519 has NOT been merged yet into the main branch. To use my fix, you need to either:

1. Clone my branch directly:

git fetch origin pull/2519/head:timeout-fix
git checkout timeout-fix

2. Or wait for the PR to be merged

If you've already done this and still experiencing issues, please check your infrastructure layer timeouts:

• Nginx: Add proxy_read_timeout 600s; to your config
• Kubernetes Ingress: Add annotation nginx.ingress.kubernetes.io/proxy-read-timeout: "600"
• Docker reverse proxy: Check your proxy timeout settings

Could you please confirm:

1. Which branch/commit are you using?
2. Are you using any reverse proxy (Nginx, Traefik, etc.)?

Thanks!

[SAljajith]

@majiayu000
Steps we have checked:

We copied and tested your code in our local environment. ( https://github.com/simstudioai/sim/pull/2519/files )

We tested the same setup using Docker Compose, but the issue still occurs.

We built a Docker image using your code and tested it; the issue persists.

Note : After 5 minutes timeout issue occurs

Could you please let us know how to configure the Docker reverse proxy timeout?

[SAljajith]

@majiayu000

All the code has been updated as part of feat(http): add configurable timeout for API block requests.
While running your code in my local environment, the timeout issue still occurs if the API runs for more than 5 minutes.
Timeout Configured in API block 10 mins

[ERROR] [ProxyAPI] Creating error response {
[App] "errorMessage": "fetch failed",
[App] "status": 500,

Running In localhost: 3000
Note : without Docker

Do I need to update any configuration? let me know.

Thanks!