output of for each node
ART-12393_KNOWLEDGE_NODE-25
with their timestamp, execution time, and the status.\n\n   If you don't see your latest run, click the refresh button on the top right of the runs view table.\n4. Click the run. The workflow overview of that specific run is shown.\n5. Click any of the nodes to see the input values and the output values of that particular step.\n\n   Click the star button to get an AI-generated actionable explanation of the error.\n\n[PreviousWorkflow
Troubleshooting | Workflows | Computer by DevRev | DevRev
ART-1976_KNOWLEDGE_NODE-25
and effective resolution. Users can design workflows tailored to various scenarios; the example below illustrates a basic routing use case.\n\n| NODE | ACTIVITY |\n| --- | --- |\n| Trigger | Ticket created |\n| Action | Pick user by group |\n| Action | Update ticket |\n|  | ID: Ticket created > Output > ID |\n|  | Group > Output > ID |\n|  | Owned by > Set: Pick user > Output > User |\n\nOrgs can set up pull-based routing by updating the group instead of the user ID in the workflow illustrated
Routing | Computer for Support Teams | DevRev
ART-15345_KNOWLEDGE_NODE-1
<token>" |\n```\n\n[Try it](/api-reference/customization/stage-diagrams-list?explorer=true)\n\n200Retrieved\n\n```\n|  |  |\n| --- | --- |\n| 1 | { |\n| 2 | "result": [ |\n| 3 | { |\n| 4 | "id": "string", |\n| 5 | "stages": [ |\n| 6 | { |\n| 7 | "is_deprecated": true, |\n| 8 | "is_start": true, |\n| 9 | "stage": { |\n| 10 | "id": "string", |\n| 11 | "display_id": "string", |\n| 12 | "name": "string" |\n| 13 | }, |\n| 14 | "transitions": [ |\n| 15 | { |\n| 16 | "target_stage": { |\n| 17 | "id":
List Stage Diagrams | DevRev | Docs
ART-1972_KNOWLEDGE_NODE-27
by Channel**\n\n  Number of tickets where SLA was breached for each source channel.\n* **SLA breaches by Subtype**\n\n  Number of tickets where SLA was breached for each ticket subtype.\n* **SLA breaches by Owner**\n\n  Number of Tickets with SLA breaches for ticket owners.\n* **Avg CSAT by SLA status**\n\n  Average CSAT rating of tickets w.r.t. their SLA status and severity.\n* **Unassigned Tickets with SLA breaches per Customer**\n\n  Number of Unassigned Tickets with SLA breaches for each
Ticket-SLA Analytics | Support analytics | Computer for Support Teams | DevRev