Inngest streaming with Fly.io

Hi - I am experiencing timeouts on long-running functions that get triggered via Inngest (inngest.com). In their docs, they suggest turning on streaming as a potential solution: Streaming - Inngest Documentation

While Inngest doesn’t call out Fly.io explicitly as a platform they support, I set streaming to force and I can see that it does now send bytes every ~3 seconds in the function call. This appears to be working/solves my problem, but I wanted to check and see if there’s anything I should be aware of on Fly’s side with this solution?

Fly doesn’t seem to document any kind of timeouts/restrictions on streaming or http requests (although anecdotally requests were timing out at the ~100 second mark before streaming). This issue almost forced me to migrate off of Fly but now there seems to be hope to stay here. Would love any insight on whether or not this approach is ok.

Thanks!

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.