Orchestration Flows

CXOps Cloud orchestrates multi-step content workflows automatically. When you trigger an action in one module, it can cascade through others — and Control gives you visibility into the entire flow.

Common Orchestration Flows

Signal → Content → Publish

The most common end-to-end flow:

1. Signals refresh runs → new signals detected (signals-refresh job)
2. You activate a signal → Cortex project created
3. Content generation runs → draft produced with SEO/GEO analysis (cortex-optimize job)
4. You run a compliance check → Govern evaluates the draft (govern-check job)
5. You approve the draft
6. You adapt for channels → channel-specific versions generated (adapt-content jobs)
7. You publish → content pushed to WordPress

In Control, you can see each of these jobs and their status as they execute.

Brand Setup Flow

When you first configure your brand identity:

1. You upload brand guidelines → document queued for analysis
2. Analysis runs → AI extracts voice, tone, terminology (identity-analyze job)
3. Indexing runs → vector embeddings created for semantic matching (identity-index job)
4. Brand is now AI Ready — all other modules can reference it

Performance Sync Flow

Ongoing measurement cycle:

1. GA4 sync runs on schedule → metrics pulled from Google Analytics (performance-sync job)
2. Aggregation runs → trends computed, goals evaluated (pulse-aggregate job)
3. Dashboard updates with latest performance data

Auto-Optimization Flow

For projects with auto-optimize enabled:

1. Nightly scheduler triggers re-optimization
2. Cortex optimize runs → content re-analyzed with current SEO/GEO data (cortex-optimize job)
3. If changes are significant, the draft is updated and flagged for review

Monitoring Flows in Control

When a multi-step flow is running, you’ll see multiple jobs in Control — one for each step. Use the product filter to focus on a specific module, or view all jobs to see the full orchestration in action.

Identifying Bottlenecks

If a flow is taking longer than expected:

• Check for waiting jobs — a backlog may indicate the system is under heavy load
• Check for failed jobs — a failure in one step blocks downstream steps
• Check active job progress — some operations (like content generation) take longer than others

Handling Failures

When a job in a flow fails:

1. Click the failed job to see the error message
2. Fix the underlying issue if possible (e.g., invalid source URL, expired OAuth token)
3. Retry the failed job from Control
4. The flow will continue from the retried step

Real-Time Updates

The Control console updates in real-time via server-sent events (SSE). When a job completes or fails, the UI updates immediately without requiring a page refresh.