Skip to content

Conversation

cnaples79
Copy link

This updates the Debugging docs to clarify that resume is useful beyond failed runs and adds concrete examples:

  • Iterate on downstream steps while reusing upstream artifacts (resume from a named step).
  • Combine resume with compute backends (--with batch / --with kubernetes) to test without re-running upstream work.
  • Safely reproduce production runs locally via --origin-run-id.
  • Detect resumed runs inside code with current.origin_run_id.
  • Link to programmatic Runner.resume for notebooks/scripts.

Fixes #38.

…erating on downstream steps\n- Show combining resume with compute backends (--with batch/kubernetes)\n- Note safe local reproduction of production runs\n- Include snippet to detect resumed runs via current.origin_run_id\n- Link to programmatic Runner.resume\n\nFixes Netflix#38
Copy link

vercel bot commented Sep 14, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
metaflow-docs Ready Ready Preview Comment Sep 14, 2025 6:50pm

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Improve documentation around resume
1 participant