EtherAssist
  • Administration
  • Agent mode
  • Integrations
  • Getting Started
  • Models and AI
  • Partner portal
  • Security & Compliance
  • Settings
  • Support
  • Supported topics
  • Tools
  • Using EtherAssist
  • Windows 11 readiness
  • PowerShell
  • Release Notes

Agent console and monitoring

The Agent console shows task progress, run history, reasoning updates where enabled, outputs, and artifacts.

Agent task console

Before you begin

  • Start or open an agent task or workflow.
  • Confirm you have access to the task, workflow, and any connected integration records.
  • Keep the source prompt and attachments available if you need to retry a failed run.

Monitor a run

  1. Open Agent Mode.
  2. Select the task or workflow from the console list.
  3. Check the run status.
  4. Review streamed progress and step-level updates.
  5. Open generated outputs or artifacts.
  6. Use run history to compare the latest run with earlier attempts.

Expected result: you can see whether the run is queued, running, waiting for input, completed, failed, or cancelled.

Review the console areas

AreaWhat to check
StatusQueued, running, waiting for follow-up, completed, failed, or cancelled.
ProgressStreaming output, reasoning updates where enabled, and step-level updates.
ArtifactsGenerated files, exports, workflow outputs, or ticket notes.
HistoryEarlier runs, follow-up attempts, retry outcomes, and workflow versions.

Take action on a run

  1. Open the run.
  2. Review the latest output and any warning or error message.
  3. Continue the result in chat when you need interactive refinement.
  4. Retry or rerun when the prompt, files, or integration state has changed.
  5. Download artifacts created by workflow actions.
  6. Archive completed work that no longer needs to appear in the active task list.

Tip: Keep completed work until the user or customer has confirmed the output. Archive after handover rather than deleting immediately.

Tips

  • Keep names, prompts, and configuration values specific to the task you are performing.
  • Check role, subscription, region, and tenant policy when a feature is not visible.

Troubleshooting

ProblemWhat to check
Run is queuedAnother run may still be active, or the worker may not have picked it up yet. Wait briefly, then retry if the status does not change.
Run is waitingAnswer the follow-up question, or rerun with follow-ups disabled when the job must run unattended.
Run failedReview the error, attached inputs, model selection, and workflow step that failed.
No artifact appearsConfirm the workflow includes an Action or export step and that the action points to the correct source output.
Output is incompleteReduce attachments, narrow the prompt, or split the work into smaller task or workflow steps.

Known issues

Long-running document packs should preserve partial progress where supported. Review the run history before restarting a large pack so you do not miss completed outputs.

Next steps