DimerIQ
Pause and resume safely
A pause saves progress; a resume creates a linked attempt.
- Open the active run and request its pause/stop action.
- Keep checking status. “Stop requested” means the worker received the request; it may still be finishing a safe step.
- Wait for the saved STOPPED checkpoint. Already saved candidates and evidence remain available.
- Choose Resume saved run when you want to continue.
- Keep the new run ID. The resumed attempt points back to the earlier run and reuses its checkpoint.
Closing your laptop, changing areas or ending an API connection does not pause the cloud worker.
A run that has already completed its search cannot simply resume. Start a new run if you want to change its inputs or scope. If a start/resume request times out, inspect saved runs before retrying: automatic duplicate submission is not safe.
For developers: inspect both the outer job status and result.data.status. A safely stopped execution can have outer status succeeded because saving its checkpoint succeeded; that does not mean its search is complete.