ChartCraft
Open studio
State Diagram Updated 4/16/2026

ATM State Diagram for Card, PIN, Withdrawal, and Error Handling

This state diagram is used to model how an ATM moves from power on and idle through card reading, PIN entry, menu selection, amount entry, processing, cash dispensing, receipt printing, card ejection, card retention after three failed PIN attempts, and out-of-service recovery. It helps clarify valid transitions, exception handling, and session outcomes for banking software teams, QA testers, ATM product managers, and operations staff.

State DiagramATMBanking WorkflowPIN VerificationCash Withdrawal
13 nodes 22 connections

Related diagrams

More examples with overlapping tags

State Diagram 4/16/2026

Support Ticket State Diagram with Escalation and Conditional Routing

A State Diagram for a support ticket lifecycle, covering New, Triage, Assigned, In Progress, Escalated, Pending Vendor, Resolved, Closed, and Cancelled, with conditions such as missing details, no response timeouts, SLA breach risk, misrouting, reopen, and vendor dependency. It is used to define allowed status changes, improve handoffs and exception handling, and help support managers, service desk teams, and operations leads standardize ticket handling.

State DiagramSupport TicketsIncident WorkflowSLA EscalationCustomer Support
State Diagram 4/16/2026

CI/CD Pipeline Job State Diagram

A state diagram for a CI/CD pipeline job maps how work moves from job created to Queued, then Running when a runner is assigned, and finally to Passed, Failed, or Cancelled before completion. It is used to define valid job status changes, helps teams reason about execution outcomes, cancellations, and automation rules, and is useful for DevOps engineers, platform teams, QA, and developers maintaining build and release workflows.

State DiagramCI/CDPipeline JobDevOpsJob Lifecycle
State Diagram 4/16/2026

CI/CD Pipeline Job State Diagram

This State Diagram is used to model how a CI/CD pipeline job moves from queued to running and then to passed, failed, or cancelled, including cancellation before or during execution and continued activity while running. It helps teams clarify lifecycle rules, runner assignment, completion outcomes, and cancellation behavior for troubleshooting and automation design. DevOps engineers, platform teams, and software developers would use it.

State DiagramCI/CDPipeline JobsDevOpsBuild Status