Errors and re-runs

Long scans run many agent jobs, and some will fail - a timeout, a flaky provider, a job that errored. open·kritt surfaces those clearly and lets you continue without repeating successful workflow steps.

How errors surface

The scan detail page includes a status summary that reports:

• Active jobs - what's running right now (up to a handful shown).
• Recent errors - the latest failures, each with a message, kind, and source.
• Latest error - the most recent problem, if any.
• Attempt counts - how many step and post-script attempts have completed, are running, or failed.

Scan-level problems are recorded on the scan itself; individual step and post-script failures are recorded per job, so you can tell whether the whole scan or just one job went wrong.

Resuming a scan

You can pause a running scan and resume it later. Failed, paused, and stopped scans continue from their completed workflow lineages. Completed step results remain available as input to later depths; only failed or unfinished work is queued again.

1. Pause

   Pause a running, prewarming_cache, or post_processing scan to halt new jobs.

2. Resume

   Resume a failed, paused, or stopped scan to continue from where it left off.

Multiple passes

Because agents are non-deterministic, a second pass sometimes finds what the first missed. Set repeat_runs in the scan's configuration to run the whole workflow more than once; each repeat is tracked independently and its findings are added to the scan.

Note

Resuming preserves the repository revision and scan configuration. Create a separate scan when you intentionally want to run every workflow depth again from the beginning.

That's the full tour. Head back to Welcome or dive into Workflows to go deeper.