Skip to content
ARGUS User Manual

Workflow tile

Workflows are event-driven automations defined at the org level (see Admin → Workflows). The Workflow tile inside the operation console lets you monitor and interact with workflow instances active in this mission.

What the tile displays

Two sections:

Workflows list

Every org workflow flagged as applicable to this operation. Per row:

  • Name — org-defined label.
  • Trigger type — Manual / Scheduled / Event / Webhook.
  • Action count — how many actions the workflow will execute.

If a workflow is Manual-triggerable, a “Trigger now” button appears.

Runs list

The most-recent 20 workflow runs, sorted newest-first. Per run:

  • Status badge — completed / failed / running / paused / waiting_approval.
  • Trigger type — which kind of event spawned this run.
  • Start time.

Click a run to expand into step-level detail.

Expanded run detail

Each step of the workflow has its own card:

  • Status (completed / failed / skipped / running).
  • Action type (webhook / Slack / email / drop-flag / etc.).
  • Attempt count — retries so far.
  • Approval decision (if the step was an approval gate).
  • Error message — for failed steps.

Interacting with runs

Running workflows can be acted on:

  • Pause — temporarily halt (the workflow keeps state, resumable).
  • Resume — unpause.
  • Cancel — terminate the run. Already-executed actions aren’t undone.
  • Approve (for runs in waiting_approval state) — continues to the next step.
  • Deny — marks the approval as denied and terminates or follows the deny-path.

These buttons fire via WorkflowService.pauseRun() / resumeRun() / cancelRun() / approveRun() / denyRun().

Triggering a manual workflow

Click Trigger now on any Manual-trigger-type workflow in the top list. The workflow spawns a new run immediately; it appears in the Runs list within a second.

What workflows can do

Actions available at the org-template level:

  • Post to Slack / Teams / Discord.
  • Fire a custom webhook with a Mustache-templated payload.
  • Send email.
  • Create a mission task.
  • Drop a flag.
  • Push to master caution.
  • Auto-generate + distribute the mission report.

Persistence

  • Org definitions — in organizations/{orgId}/workflows/.
  • Run state — streamed via WorkflowService.listOperationRuns() (real- time subscription on this mission’s runs).

Known limitations

  • No editing from the tile — workflows are designed at the org level. The tile is monitor + act, not author.
  • No role-gating for pause / resume / approve / deny in the tile UI; the WorkflowService enforces server-side role checks but the UI shows all buttons to everyone.
  • Error-display is a plain alert / toast — no inline rich error UI.