Streaming timeouts (vercel world)

[agamm]

Is this something I should extend the max duration in vercel.json?

It seems like it should work out of the box, no?

I'm using streaming if it helps.

[andreisocaciu]

I've set mine to 600 seconds and it still times out. Using streaming as well.

[TooTallNate]

Not a lot of information to go off of here, but this is probably fixed by #678.

[Skorch]

Not a lot of information to go off of here, but this is probably fixed by #678.

I was also seeing these timeouts (the actual workflow didn't seem to be affected)

After updating to 4.0.1-beta.45 I haven't seen any of these timeouts.

[pranaygp]

@agamm please update to the latest version. also make sure you're releasing the lock on the writer when you're done using it.

the errors you're seeing aren't problematic (the workflow still continues) but it unnecessarily leave the request running because the process still has a lock on the stream

[Thyrst]

Hello, it is still happening for me with workflow@4.0.1-beta.48 even after calling writer.releaseLock in the step.

Here is a snippet to reproduce it: https://gist.github.com/Thyrst/0cdab048d6e342830a3633ab6aa14e6b

[VaguelySerious]

Hi @Thyrst, is this still happening for you on the latest version? If so, I'll re-investigate

[Thyrst]

Hi @Thyrst, is this still happening for you on the latest version? If so, I'll re-investigate

Hello @VaguelySerious, I just tested version 4.1.0-beta.60, it is still happening.

Here is whole repo with the repro code: https://github.com/langtail/test-workflow
After deploying to Vercel, starting the workflow and waiting 5 minutes, this is the error I see in logs:
Vercel Runtime Timeout Error: Task timed out after 300 seconds

[ceolinwill]

I’m seeing the same Task timed out after 800 seconds errors on 4.2.0-beta.71 with a Next.js App Router app deployed to Vercel. The steps complete successfully, but the functions don’t terminate and appear to hang. The pattern matches what was described here (getWritable(), write, releaseLock() in finally).

Could you confirm whether this is still expected on the latest version? Also, is there anything we should be doing on our side or is this pending a fix?

[ceolinwill]

With Claude Code help, I managed to reproduce this in a test, have a look: #1518 @VaguelySerious @TooTallNate