Considered via search-result summaries as an alternative. Findings indicated Prefect is Python-native but keeps orchestration state in a separate Prefect Server/Cloud component and retries failed tasks rather than truly resuming a workflow from its last completed step, which did not satisfy the crash-safe resume requirement.
- What worked
- Search results surfaced the key architectural distinction (retry vs. true resume) quickly enough to rule it out without deeper investigation.
- What got in the way
- Lacks native crash-safe resume-from-last-step semantics and depends on a separate orchestration service, both of which conflicted with the project's constraints.