Skip to main content

Missing events

When your point-of-sale system sends an event for a guest who isn't a member yet, or a rule fails while processing an event, the member never gets their points. Missing Events collects those events so you can fix the cause and send them through again.

Before you start​

You need event-engine:unprocessed-events:read to see the page. Retrying and dismissing events needs event-engine:unprocessed-events:write. Without it you can read the list but not act on it.

Read the list​

Open Customers then Missing Events. Each row shows:

  • Event date
  • Event type, with its code underneath
  • Reason: No matching member or Rule failed
  • Member: Matched when the event named a known member. Otherwise the name, email or phone it carried, or "No identifiers".
  • Why, a short explanation of what went wrong
  • Status: Open, Resolved or Dismissed

Use the Status, Reason and Event type filters to narrow the list. You can save a combination of filters as a view. If nothing is waiting, the page says "No open events. Everything that came in was processed or handled."

A banner appears if some event types don't keep events that match no member. For a coffee chain's "Purchase" event, that means a sale by an unknown guest leaves no trace here. Open the event type and turn on Save unprocessed events if you want those events to show up.

Look at one event​

Select a row to open it in a side sheet with the details of what the event carried and why it wasn't processed. From the sheet you can dismiss that one event. You can retry it only if the event's data was kept. When it wasn't, the sheet offers Dismiss alone.

Retry events​

Retrying sends the event back through your rules. Fix the cause first, for example by creating the missing member or correcting a rule, then retry.

  1. Filter the list to Open events. Only open events can be selected.
  2. Tick the events you want, up to 100 at a time.
  3. Choose Retry.

A summary appears above the table. It says how many events were processed and how many are still unprocessed, and lists any the retry skipped. Open a still-unprocessed event to see why.

For an event with no matching member, open it and pick the member it belongs to. The retry then runs for that member. This is available only when the event's data was kept.

Dismiss events​

Dismiss events you don't want processed, such as test events from an old system.

  1. Select the open events, up to 100 at a time, or open a single event.
  2. Choose Dismiss.
  3. Under Why are you dismissing them?, write a note. It's required, and it's kept with each event.
  4. Select Dismiss.

Dismissed events leave the open list and aren't processed.