A step where nobody does anything
A support agent cannot work a ticket without the customer's order number, so the flow asks the customer for it. Draw that on a Grid and you get Start → Ask for the order number → and then a box that should say what happens next. Nothing happens next, not inside the flow. It waits for something outside it: the customer replies, or enough days go by that the team closes the ticket. Most boxes in a flowchart are something someone does. This step is something that happens.
BPMN (Business Process Model and Notation, the standard many workflow engines execute) draws the two differently. A rounded rectangle is a task, work a person or a system performs. A circle is an event, something that happens: a message arrives, a date comes round. The border says where the event sits: a thin single line for a start event, a double line for an intermediate event somewhere along a path, a thick line for an end event. A marker inside names the trigger: a clock for a timer, an envelope for a message. An event can also be catching, waiting for its trigger, or throwing, making it happen, such as sending a message instead of receiving one. The pause in the ticket flow is an intermediate catching event: the path reaches it and stays put.
The Grid draws none of these circles. Its Start and End play start and end events once the title names the trigger ("Customer writes in"), and two stencils cover the waiting: the Delay ("Wait state") and the Event Gateway ("Branch on first event"). There is no clock or envelope, so the card's title has to say which event it stands for.
The ticket waits for two things at once
A single timer is the easy case: the path arrives, sits until the time has passed, and carries on. A Delay draws exactly that; Connectors, off-page links & delays introduces the stencil. The ticket is harder, because it waits for two events and only the first may count. A reply on day 2 must stop the seven-day clock, or the ticket gets closed under a customer who answered. Silence must still end the wait, or the ticket stays open for ever.
BPMN draws this with an event-based gateway: a diamond whose outgoing paths each begin with a catching event, or with a task that only receives a message. The process waits at the gateway. The first event to occur takes the flow down its path, and the others stop waiting. Gateways: parallel, inclusive & event places it among the other gateways; the Grid's Event Gateway takes up to three such paths.
The Event Gateway races two events. The first to happen decides the path; the other stops waiting.
The left path opens with an Input/Output card standing in for the message, since the reply is data coming into the flow; the right path opens with a Delay standing in for the timer. Neither card is a BPMN event, and nothing in the drawing shows that the losing path is abandoned the moment the other fires: the Event Gateway's meaning carries that. So title both cards as things that happen ("Reply arrives", "Day 7"), not as work ("Check inbox").
The same Delay means two different things in the two places it can sit. In a straight line, it is a wait the flow always sits through in full. After an Event Gateway, racing the reply, it is a deadline that matters only if nothing happens first. That is the difference between pausing and timing out. A "Wait 7 days" card placed right after "Ask for order", with no race, does not close silent tickets after a week: it makes every customer wait a week, and the reply has nowhere to arrive. How timeouts behave in a running system is the subject of Timeout.
Events pinned to the edge of a task
BPMN has a second way to draw that deadline. Make the waiting a receive task, "Await reply", which completes when the reply arrives, and attach a timer to its border. That is a boundary event: a catching event that listens only while the task it sits on is running. When an interrupting boundary event fires (a solid double line), the task is cancelled and the flow leaves through the event's own path instead of the task's normal exit. Closing the ticket on day 7 is interrupting: once the timer fires, nobody waits for the reply any more. The race above reaches the same outcome, because the paths after an Event Gateway exclude each other.
A non-interrupting boundary event (a dashed double line) fires without cancelling anything: the task keeps running and a second path starts beside it. That is the reminder. On day 3, if the customer still has not answered, send a nudge and keep waiting.
No flow card on the Grid attaches to another card's border, so a non-interrupting event becomes a path of its own, forked off with a Parallel Gateway before the wait starts. Here "Await reply" stands for the whole race of the first diagram:
The side path stands in for a non-interrupting timer. The No reply? check approximates what BPMN does for free: no reminder starts once the wait is over.
The drawing gets the timer right but does not tie the side path to the wait. In BPMN the boundary timer listens only while the task runs: a reply on day 1 completes the task before the timer fires, so no reminder starts (a reminder path that already started carries on). The forked path does not know the wait has ended. It sleeps its three days anyway, and only the "No reply?" check keeps it from nudging a customer who answered two days earlier; leave the check out and the diagram promises a reminder the process would never send. (The side path ends at its own End, so nothing has to join it, though the flow now lasts at least until day 3 even when the reply came on day 1.)
Failures have an event too, the error boundary event, and the Grid approximates it with a Decision that routes to an Error Boundary card; Error handling & error boundaries covers that path.
Green, until something happens
A traffic light runs on both kinds of wait. Yellow and red are pauses: a Delay each, sat through in full. Green is a race, the green phase timer against a pedestrian pressing the button, and whichever comes first ends it. The Traffic Light Controller challenge asks for exactly that, an Event Gateway holding green, with the pedestrian's path still passing through yellow and red before the walk signal. There is no reference solution to compare against; the grader reads your diagram against the brief's requirements.