Jobs & outcomes
After you run a spinner, CXGear stores results in two related places: Jobs (the run) and Records (each contact’s outcome).
Jobs page
Section titled “Jobs page”Jobs lists every run for the project.
- Left: runs (spinner name, progress, status, duration)
- Right: records for the selected run (paginated)
- Refresh updates the list (no constant auto-refresh flicker)
Each job shows started, ended (or in progress), and total time.
Screenshot needed
Jobs page: runs on the left, records on the right, Refresh in the header.
Where: Project → Jobs
Save as:
src/assets/screenshots/08-jobs-page.pngRecords page (ops view)
Section titled “Records page (ops view)”Records is for supervisors and operators. It answers:
- Who was contacted? (metadata fields)
- What happened? (disposition, AI reply, message ids)
- When? (completion time)
- Which spinner?
Rows are single-line with long text truncated. Click a row to open a detail panel below the table — not the debug journey.
Screenshot needed
Records list with compact rows and detail panel open.
Where: Project → Records
Save as:
src/assets/screenshots/09-records-outcomes.pngWhat is stored (and why)
Section titled “What is stored (and why)”| Stored data | Why it matters |
|---|---|
| Metadata payload | Contact context that entered the pipeline |
| Outcomes | Disposition, AI text, channel references — decisions and follow-up |
| Status / timing | SLA and ops reporting |
| Journey events | Debug only (step logs and errors) |
Internal fields such as log bookkeeping and model names are hidden from the main outcome list so the screen stays useful at high volume.
Pipeline journey
Section titled “Pipeline journey”Use Pipeline journey from the detail panel when you need step-by-step debug (log templates, function console.log, AI errors). See Pipeline journey.