Workflows
Workflows
The Workflows page lists workflows that Aiden can match to inbox requests. Create or edit the full workflow definition in Workspace Settings.
Open Aiden DevOps -> Workflows (under Configure). Subtitle: Workflows matched to inbox requests. Create or edit them in Workspace Settings.
View vs create and edit
| Action | Who | Where |
|---|---|---|
| Browse the DevOps catalog, search, open a card | Admin, Workspace Admin, Workspace User | Aiden DevOps -> Workflows |
| Create metadata, edit stages, publish versions | Admin, Workspace Admin | Workspace Settings -> Workflows (also reached from New Workflow / Edit) |
Workspace Users can still override which workflow runs on a request in the Requests Inbox when they approve.
Page actions
| Control | What it does |
|---|---|
| New Workflow | Starts creating a workflow (opens the workspace workflow create experience) |
| Search workflows | Filters the catalog |
| Edit | Opens the workflow for editing (admins) |
Catalog
Each card shows:
- Category (for example platform-engineering, infrastructure-as-code, incident-response)
- Workflow name
- Short description
- Publish state (for example Published)
The page also shows the total workflow count.
Write descriptions that match tickets reliably
Triage matches tickets using workflow descriptions (and related example queries on the platform side). Prefer specific, distinct wording.
Good examples:
Provision a temporary S3 bucket in the named AWS account and region, then comment the bucket name on the ticket. Do not delete existing buckets.Rotate the staging Postgres application password in Vault, update the linked secret, and comment when complete. Never touch production.Investigate a failing GitHub Actions workflow run named in the ticket, summarize the failing job log, and suggest a fix. Do not push commits.
Bad examples:
Handle infra requests(too broad; overlaps everything)Do the usual access stuff(no service, environment, or success criteria)- Two workflows both described as
Fix CIwith no pipeline or repo scope (matching cannot tell them apart)
Overlapping workflows
When two descriptions are near-duplicates, Aiden may pick either or match poorly. Fix by:
- Narrowing each description to a unique trigger (environment, system, or outcome).
- Adding distinct Example Queries on the platform workflow form.
- Overriding Workflow to run on approve on the request when a one-off correction is enough.
- Retiring or unpublishing the weaker Active version.
From suggested draft to executable workflow
- In the Requests Inbox, when no workflow matched, click Describe Workflow and describe the procedure in plain English.
- Review the suggested draft (stages and integrations). Treat it as a starting point, not production truth.
- An Admin or Workspace Admin opens the workflow under Workspace Settings -> Workflows, adds stages, agents, tools, and runbooks, then runs a test.
- Publish an immutable version as Candidate, then promote to Active when ready for matching traffic.
- Confirm a new matching ticket selects that workflow in the inbox, then approve safely.
Full stage, publish, and failure-handling detail lives on the platform Workflows page.