Jobs Tray
Monitoring background jobs and workflows in GridWonk.
Salesforce connector work
Salesforce connector operations have their own durable import and delivery records; the connector remains disabled pending acceptance. A generic job identifier or utility role does not grant access to captured source data. Ordinary cancel, reprocess, and review controls cannot bypass the source-managed import gate. After activation, inspect connector progress and its explicit quota, provider, or processing wait reason.
Job Types
The active transitional job appears in the tray as Compliance Validation.
| Job Type | Description |
|---|---|
| Document Discovery | Locating relevant utility procedure documents |
| Packet Review | Reviewing the uploaded packet against published requirements |
| Compliance Validation (Transitional) | Existing upload and screening flows can still start the legacy single-document workflow until PR11 |
| Document Digitization | Processing your uploaded PDF documents |
| Finding Locations | Pinpointing deficiency locations in your documents |
| Generating Report | Creating scorecard and deficiency reports |
Older job history can also show Requirements Extraction. Packet Review is the canonical packet-intake path; the other labels belong to the legacy path that PR11 will remove.
Status States and Icons
| Status | Icon | Color | Meaning |
|---|---|---|---|
| Pending | Clock | Gray | Waiting to start |
| In progress | Spinner | Blue | Currently running — the badge shows the specific active state (discovering, parsing, extracting, fetching, analyzing, or validating) |
| Complete | Checkmark | Green | Successfully finished |
| Failed | X | Red | Error occurred |
The tray auto-expands when jobs start so you can monitor progress. An idle tray floats as a small Jobs pill at the bottom-right instead of holding a full-width row; select it to open the job history. Speech-input users can address it by the word it shows, Jobs. With no job history at all, the idle tray renders nothing.
Workflow Grouping
Related jobs are grouped into workflows showing the complete pipeline:
Example: Transitional Single-Document Workflow
- Digitize (Prepare your document)
- Validate (Check one document against legacy requirements)
- Locate (Mark deficiency locations)
- Report (Generate scorecard)
This grouped display describes the transitional workflow, not packet Review. Packet Review has its own submission-scoped run history.
Reliability and Delivery
GridWonk now runs pipeline stages with durable orchestration and queue-backed dispatch for long-running tasks. For users, this means:
- Lower chance of stalled multi-step workflows
- Better retry behavior for transient provider failures
- More consistent completion/failure states in the jobs tray
- Packet review and related document processing use durable workflow paths
You still use the jobs tray the same way; these changes improve execution reliability behind the scenes.
Progress Monitoring
The permission-aware live-update rollout is gated until database and browser checks pass. Once enabled, the tray reconciles missed completed/failed jobs through authorized reads, keeps current data during transport failures, and removes jobs only when reads confirm they no longer belong in the current view. Pagination is not evidence of removal. Existing tabs need a refresh after rollout.
Short interruptions are silent. After eight seconds the header distinguishes Connecting live updates… from Live updates interrupted — reconnecting…. Successful periodic refreshes stay quiet. Document, finding and project changes also have scheduled refresh coverage because not all changes emit job events. A successful jobs read cannot hide a failed read elsewhere. Some live updates are unavailable. offers Retry updates without a page reload or a new job. Offline browsers warn that displayed information may be out of date; expired sessions offer Sign in. A successful reconnect alone never proves that displayed data is current.
Each job displays:
- Progress bar — Percentage complete (0-100%)
- Current step — Description of current activity
- Completion stats — Items processed vs total
Click any job to see detailed timeline, individual step status, and results.
Cancel and Retry
Cancel a packet review
Use Review Actions → Cancel Packet Review in the project when your review permissions allow it. Cancellation settles the linked run and prevents further packet results from that run; completed document findings stay available. A provider request already running may finish in the background. The project action warns when stopping the background workflow cannot be confirmed, including older runs whose runtime identity is unavailable. Read that warning and contact support before starting another packet review.
Cancel
Use Cancel to mark an active job as failed with Cancelled by user and remove it from the active tray. This status change is not a guaranteed hard stop for work already dispatched to an external worker. Outputs written before cancellation can remain, so check the destination before starting the workflow again.
Retry
Some surfaces expose targeted retry actions, such as retrying upload digitization or report generation from the Results panel. The jobs tray itself supports canceling active jobs and removing history; do not rely on a generic failed-job retry creating a new job entry.
Remove from History
Use Remove from History to clear completed jobs from the list. This does not delete any actual results.
Best Practices
- Let jobs complete before canceling unless necessary
- Review error messages before retrying
- Monitor discovery and packet-review jobs; duration varies with source size and provider response time
- Clear old jobs periodically