What's the chance "IoContext timed out due to inactivity" is caused by script upgrade?

Hoping someone with a better understanding of Durable Object RPC internals can help here. I'm seeing these two logs:

Error on connection BOBOqEAOPI in Sessions:xxx:
Error: This script has been upgraded. Please send a new request to connect to the new version.

Error on connection BOBOqEAOPI in Sessions:xxx:
Error: This script has been upgraded. Please send a new request to connect to the new version.

and in the same EventTimestampMs

IoContext timed out due to inactivity, waitUntil tasks were cancelled without completing.

IoContext timed out due to inactivity, waitUntil tasks were cancelled without completing.

I'm sending a ReadableStream over RPC from an AI workflow which is long running. Obviously when scripts upgrade (deployment or Workers platform decision) it terminates the RPC streams. My theories - ReadableStream terminates due to script upgrade -> IoContext times out - in other RPC calls (not long-running) we're also seeing this. It feels like stubs are kept open? My dispose hygeine is... not great at this time; but I thought it was not a hard requirement. Is it?

0 Replies

No replies yetBe the first to reply to this messageJoin

Gaming

Programming

What's the chance "IoContext timed out due to inactivity" is caused by script upgrade?

Did you find this page helpful?