Skip to main content
When you launch a sprint, CiCi freezes the study setup and creates the APM tasks required by the selected scenarios, variants, repetitions, and models.

​
Before launch

Confirm that:
  • The intended behavior is specific
  • Signals and mapping rules are complete for the planned study
  • Scenarios represent the workflow you intend to evaluate
  • Variant identities are correct
  • Repetitions and coverage match the decision you need to make
  • The budget and run plan shown at launch are acceptable

​
During the run

CiCi executes APM tasks in bounded parallel batches. The sprint records completed, queued, and failed work so execution can continue safely after an interruption. You can pause a sprint. Calls already in flight are allowed to settle, but CiCi does not begin the next batch. Resuming continues the remaining work without intentionally scoring completed tasks twice.
Execution progress answers whether the runs finished. It does not answer whether the evidence is sufficient or validated.

​
If a run is interrupted

CiCi uses task identity, leases, and checkpoints to recover unfinished work. If the execution deadline approaches, it creates a continuation instead of relying on one long-running task to finish the entire sprint. If progress remains unchanged for an unusual amount of time, record the sprint reference and contact your CiCi operator rather than launching a replacement sprint.