Before you start
Monitor presents execution-attempt evidence. A saved or published Workflow is a definition, not an attempt. Keep the run identifier, approximate time and involved revisions. Select the authorized tenant and review read permission plus permission for each operational action.
Do not share input rows, credentials, cookies or unfiltered logs in an incident. A useful report includes state, task and a safe message without sensitive content.
Procedure
- Open Monitor and narrow results by name, state or time. Check identifier and date: one Workflow can have multiple attempts.
- Distinguish active from terminal states. Waiting for capacity differs from failure; cancellation and success are also different outcomes.
- Open attempt details and inspect tasks and dependencies. Find the first relevant error, not merely the last skipped task.
- For waiting, inspect worker, slots and execution context through authorized surfaces. Do not launch a duplicate because the grid is slow to refresh.
- Before cancelling, terminating, recovering or repeating, refresh state and review that action’s confirmation.
Synthetic example
Use a laboratory Workflow with synthetic CSV input. Run once with a correct path and again with a nonexistent path in the same laboratory. Locate both attempts by identifier. In the failed one, identify the affected task and missing-file message. Correct the binding and start a new attempt; retain earlier evidence according to the applicable policy.
Verify the result
For the successful attempt, compare the produced file with expected headers, row count and values. Success records execution outcome but does not independently verify the business rule. For the failed attempt, confirm that the explanation identifies the first error and that the new attempt uses corrected configuration.
Keep history cleanup separate: it does not cancel active work or replace a retention policy. Review scope and confirmation before removing evidence.
Troubleshooting
An empty grid may reflect filters; it does not prove server failure. A client timeout does not prove cancellation: query the attempt again. Recovery depends on available compatible checkpoints and does not automatically reverse external writes. Repeating may create another output or duplicate a load. If state changes while a dialog is open, reload before confirming. For provider errors, record only the safe message and time.
Compact logs and live execution progress
The log presents Timestamp and Message columns in compact single-line rows. Expand a record to inspect its formatted, color-highlighted structured detail; collapse it again to save space. Filter with Search log messages, Level, Component and Time zone; inspect level counts, Errors only and Download log. Follow tracks new messages when you are at the bottom; Pause/Resume pauses presentation only and does not stop execution. Wrap fits long lines.
While details are visible, the view polls changes and retains previous data during delays or temporary failures. Cards use the latest reported counters. Progress can show phase, batches, processed/written rows, rate, duration and bytes when known. Staging, processing and writing are different phases: zero rows before reading do not establish inactivity. No percentage is invented without a reliable total.
The worker records safe causes such as an input exceeding the profile maximum or a protected existing destination, with available phase and limit details. Credentials and private provider responses remain excluded. For an old attempt without its original exception, a generic message remains incomplete evidence; do not assign an unrecorded cause.
List and Gantt
The list updates cells without replacing the whole table and preserves selection, filters and scroll. List and Gantt share filters. The compact Gantt distinguishes Workflow, Session and Mapping through kind and hierarchy; a Session appears under its Workflow. Open the specific attempt to inspect state, duration and versions. A Workflow bar spans orchestration; a Session bar represents that execution and must not be added again as extra Workflow duration.
Compact reading and stable updates
List aligns Execution, Duration and Status in compact rows. Purple WF and green SES badges, with the same icons as the workspace tabs, distinguish Workflow and Session in both List and Gantt; color indicators accompany the written state, and hierarchy can be expanded. Gantt text and tooltips follow Dova typography with lighter weights for labels and values.
Updates change existing rows and insert new executions matching the filters without visibly clearing or rebuilding the entire list. Selection, filters and scroll are retained. An execution outside the current filters does not need to appear.
TRACE is optional detail generated according to published Workflow and Session settings. Monitor's level filter chooses which existing evidence to display; it does not enable TRACE generation. Inspect Session inheritance when a Workflow and its tasks have different TRACE counts.
Environment context
Before using this module, confirm Tenant, Domain and Environment in the user menu. The initial environment is Development. Module, Domain and environment capabilities apply together; Production is read only without explicit authorization. Switching the selector does not move artifacts or publish or execute their data. See environments and recovery and environment promotion.
Conversation and environment
DovaAI uses the authorized Tenant, Domain and Environment and selected artifact. Switching context cancels earlier requests and starts a conversation for the new environment. A pending reply from the earlier context is not added to the new conversation. The server verifies environment identity and versions; form values, records and credentials are excluded from context.
Worker availability and view loading
A reference to a removed worker or a worker with an invalid identity does not prevent you from opening Overview, Monitor or Connections. That reference is not available for execution; valid workers remain visible within your permissions. A real storage or policy failure is reported as an error and is not converted into a zero counter.