Trigger Lab

Send an event. See what changes.

This is a browser simulation. No emails, devices or external services are connected. An event ID lets the receiver recognise a duplicate. An approval gate pauses before an action.

  1. Send a normal event: the action count rises once.
  2. Replay it: the count stays put.
  3. Send an approval-gated event: decide whether it should act.

In a real system, duplicate protection must survive restarts and handle simultaneous requests. This lab demonstrates the rule in one browser session.

Event controls

Current event: No event yet

Ready

Simulated actions completed: 0

Event record

Newest first. The last 12 entries are shown.

    Try the same rule in a plan

    What identifies one event? Where should the workflow pause? Who can approve it, and what happens after a rejection?

    Open Workflow Planner