Is it possible to limit the execution of a workflow, for example max 5 publish workflow per second or concurrently ? many apis like the openAI one are rate limited
at 4:59 - How does casting a regular error `as NonRetryableError` do anything at all...? surely you'd need to throw an error that could be introspected at runtime as a different kind of error, rather than only via the type system?
Every one of the endpoints in order where you have built in retry and exponential backoffs and can sleep for a specific timeframe, all in one reportable execution. Values of each step are memoized. Think an opinionated queue like solution with timers
spent a week building a workflow without workflows using cron triggers. I can imagine how powerful this thing is.
D1-LINER SO GOOD
Mate, any chance of a Cloudflare t-shirt?
Any chance?
Come see us at an event!
Is it possible to limit the execution of a workflow, for example max 5 publish workflow per second or concurrently ? many apis like the openAI one are rate limited
Yep this is configurable at the step level
@@craigsdennis thanks for your answer , can you give me a link to the doc for this ? I was not able to find anything
Instead
If (true) {do}
Go with
If (false) return
do
at 4:59 - How does casting a regular error `as NonRetryableError` do anything at all...? surely you'd need to throw an error that could be introspected at runtime as a different kind of error, rather than only via the type system?
Nice eyes! You're right I was recording in BETA and it was abstract so I was avoiding the squiggle. It works like you think it should now.
Is this Step Functions 🦋
I want to find more difference from Queues besides the built-in retry logic
Every one of the endpoints in order where you have built in retry and exponential backoffs and can sleep for a specific timeframe, all in one reportable execution. Values of each step are memoized. Think an opinionated queue like solution with timers