Zap Run History Replay Integration Block for React

RUNS holds every row: the Zap's name, the form, the outcome (success, halted or held), the step it stopped at and why in words, and when it ran as fixed text. The chain, the captions, the state, the tally and the status sentences are all worked out from that array, so adding a run or changing its outcome needs no other edit.

No. Replay marks the run as replayed on this page, turns the row to Success and says so in the status line. Hook your own handler where you hand the submission to the Zap again; the demo never contacts Zapier. Zapier has its own replay for unsuccessful runs in its Zap history, and this block does not call it.

They follow Zapier's own wording for a Zap run: a halted run was stopped before it finished, and a held run is paused until something it needs, such as a reconnected app account, is fixed. The reason line under each state is example text. Success runs show no reason.

The table has a caption, column headers and a row header per Zap. The dots are drawn for sighted users and hidden from assistive technology, because the caption beside them ("Stopped at step 2 of 3") says the same. Every Replay button names its Zap. The table scrolls in a focusable region if a column does not fit.

A replayed row keeps a line for its note, so "Replayed in this demo." takes the place of the reason, and the Replay button leaves an empty slot of the same width. Nothing below a row moves.

On a phone the Steps and When columns fold under the Zap's name and the Replay button shows its icon only, still named for screen readers. In a right-to-left layout the table mirrors; the chain of dots is a drawing and keeps its own order, and times and counts keep their own direction.