Control Use Cases

Monitoring a Batch Content Run

A marketing team activates 10 signals at once, creating 10 Cortex projects. They switch to Control to monitor all 10 content generation jobs in real-time. The queue stats show 10 active jobs in the cortex-optimize queue. As each completes, the team can immediately review the generated drafts.

Key features used: Queue stats, real-time updates, product filtering

Debugging a Failed Generation

A Cortex draft gets stuck in “generating” status. The marketer opens Control, filters to the Cortex queue, and finds the job has failed. The fail reason shows “Unable to scrape source URL — 403 Forbidden.” They update the project with a different source URL, create a new draft, and the retry succeeds.

Key features used: Failed job inspection, fail reason messages, retry

Weekly Cleanup

Every Friday, the operations lead opens Control and clears all completed jobs from the past week. This keeps the console focused on active and pending work. They also review any failed jobs from the week — retrying transient failures and investigating persistent issues.

Key features used: Clear completed, batch purge, weekly review

Tracking Brand Setup Progress

A new client onboarding involves uploading a 30-page brand guidelines PDF. The account manager watches Control as the identity-analyze job processes the document, followed by the identity-index job that creates embeddings. Once both complete, they confirm the brand’s AI Readiness badge is active.

Key features used: Job lifecycle tracking, identity queue monitoring, sequential job visibility

System Health Check

Before a major content push, the team lead checks Control for any failed or delayed jobs. The health banner shows green — no failures, no backlog. They proceed with confidence that the system is ready to handle the workload.

Key features used: Health banner, queue depth monitoring, system status