Removed feature: WorkflowCheckpointer migration #18

Closed
opened 2026-02-16 02:16:06 -05:00 by yindo · 1 comment
Owner

Originally created by @YutackPark on GitHub (Aug 16, 2025).

Seems like the feature is removed and there's not replacement for it.

Is there any plan for alternative feature?

If not, I'm thinking about simply dump a context into a json file and load later for restart, but not sure how to re-start from a specific step.

Originally created by @YutackPark on GitHub (Aug 16, 2025). Seems like the feature is removed and there's not replacement for it. Is there any plan for alternative feature? If not, I'm thinking about simply dump a context into a json file and load later for restart, but not sure how to re-start from a specific step.
yindo closed this issue 2026-02-16 02:16:06 -05:00
Author
Owner

@logan-markewich commented on GitHub (Aug 18, 2025):

No concrete plan yet -- the checkpointer was a little invasive, and had many edge cases that were broken

You can simply save the context as you said. It will restart at the top of whichever step was in progress. So you might do something like this at the steps you want to save

@step
async def my_step(self, ctx: Context, ...):
  ctx_dict = ctx.to_dict()
  ....
@logan-markewich commented on GitHub (Aug 18, 2025): No concrete plan yet -- the checkpointer was a little invasive, and had many edge cases that were broken You can simply save the context as you said. It will restart at the top of whichever step was in progress. So you might do something like this at the steps you want to save ``` @step async def my_step(self, ctx: Context, ...): ctx_dict = ctx.to_dict() .... ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/workflows-py#18