Concurrent runs

Overview

Concurrent validation runs are limited by subscription tier and available agent fleet capacity. When limits are reached, new runs enter a queued state until agents complete in-flight jobs. Queued runs are not failures; they indicate capacity planning is needed before peak events such as release week or large migrations.

Enterprise customers negotiate dedicated endpoint agent pools or higher concurrent ceilings in the account agreement. Standard plans prioritize fairness across organization members.

Who should read this

• QA engineers, SREs, platform teams, and developers operating Zof Console and APIs.

When to use this workflow

• Onboarding new team members to Zof terminology and workflows
• Authoring internal runbooks aligned with Console labels
• Designing CI/CD or webhook integrations against documented behavior

Step-by-step procedure

Key concepts

Queued run

Run accepted but waiting for agent capacity; visible in Operate → Runs with queued status.

Active run

Run currently executing cases on cloud or endpoint agents.

Fleet capacity

Sum of online agents multiplied by per-agent concurrency policy.

Best practices

• Stagger heavy nightly suites across teams and time zones
• Use endpoint agent pools for dedicated capacity in enterprise deployments
• Cancel duplicate runs triggered by webhook retries to free capacity
• Alert when queued depth exceeds SLO; page platform team before release freeze

Common issues

Runs stuck queued > 30 minutes

Agents offline or misconfigured; check Agent Console heartbeats.

Sudden queue spike

Multiple pipelines triggered same suite; dedupe with concurrency groups in CI.

Related documentation