[gavmor]

Very fun, and immediately useful. Also something I haven't seen before? So, kudos on an an ingenious choice of projects.

That being said, I almost immediately ran into 429: Too Many Requests.

Like, yeah, I started making a ton of `{increment: 1}` requests that are getting dropped. What's the bottleneck? Simultaneous DB writes?

Edit: I do want to reiterate that I think this is a great concept, especially in a "Shift Left" era in which agentic tools are exposing non-technical roles to the domain of workflow automation and async job queue management.

[clav88]

Thanks very much! There is some rate limiting being applied so that costs don’t explode. If people are willing to pay for it, the rate limiting can of course be reduced a lot.

I was thinking that sharing and monitoring progress is more useful for longer processes where an update every 10 or 30 seconds could be enough in most cases. What’s your use case?

Alternatively, I’ll clean up and open source the code soon. Then you can run the service yourself without rate limiting if you like.