Dapr Workflow: code that picks up where it left off
Lots of the work I see in projects is a chain of steps: fetch a document, convert it, call a model, write the result somewhere. You write it as a background job that reads from a queue, and it works fine until the process restarts halfway through a 300-page PDF or a model call times…