Lewati ke konten

Automation Run History in IZI

Опубликовано: · Обновлено: (6 дней назад)· IZI Team

Konten ini belum tersedia dalam bahasa Anda.

Run history is the log of every time an automation rule checked a client event: ran its actions, skipped it by conditions, or failed. It is the main troubleshooting tool: if a bonus was not credited or a notification did not arrive, the answer is here.

In the sidebar, switch to the organization → Marketing → Automation → Run history. The latest runs are on top.

Filters above the table: All rules, All clubs, All statuses, All events.

ColumnShows
RuleRule name; an archived rule is marked «(deleted)»
StatusRun result
EventThe event that started the rule
ClubThe club where the event happened
ClientThe client the rule ran for
Started atRun date and time

Click a row to open «Run details»:

  • Overview — rule, status, event, club, client, start and completion time; on failure, the Failure reason;
  • Variables — event variable values at run time: top-up amount, session length, age and so on;
  • Actions and Result — which actions ran and what they returned;
  • Technical details — the full error text.

A rule runs once per event: a repeated delivery of the same event does not create a second run.

StatusMeaning
SucceededConditions were met and all actions completed. Bonuses are credited, the push was sent
SkippedThe event happened but the rule’s conditions were not met. Actions did not run
FailedAn action or the formula failed; the following actions did not run
PendingThe run has started and has not finished yet

Every run with the Failed status creates an «Automation failed» notification in the Notifications bell in the CRM header of the club where the event happened. Mark all as read clears the counter.

The rule saw the event but the conditions were not met.

  1. Open the run and look at Variables — the values the conditions were checked against.
  2. Compare them with the rule’s conditions: the threshold may be too high.
  3. Check the client’s figures in their card: play time, spending, balances, groups.

More → Conditions in rules.

Open the run and read the Failure reason. Common causes:

  • the formula gave a negative amount or divides by zero;
  • a group from the action was deleted;
  • the push could not be delivered to any of the client’s devices;
  • the client is banned in the club, so bonuses cannot be credited.

A formula that rounds to zero is not an error: the action is simply skipped.

The rule did not see the event for this client. Check that:

  1. The rule is enabled and not archived.
  2. Today is within the rule’s Active period.
  3. The client’s club is in the rule’s Clubs field.
  4. The event actually happened — in the transaction history or the client card.
  5. The client is not a staff service account: rules do not fire for them.
  6. For «Birthday» — the client’s birth date is confirmed in the club.

Bonus credits and debits by automation are visible in the client card in the bonus balance operation history. Balance management → Managing a client’s balance.

Pertanyaan yang sering diajukan

Where do I find the runs of a specific rule?

In the organization menu: Marketing → Automation → Run history. Pick the rule in the «All rules» filter — only its runs remain.

What does the «Skipped» status mean?

The event happened and the rule saw it, but the conditions were not met, so the actions did not run. This is normal filtering, not an error. For example, the client topped up less than the threshold in the condition.

How do I learn about a rule failure without opening the history?

Every run with the «Failed» status creates an «Automation failed» notification in the «Notifications» bell in the CRM header of the club where the event happened.

Can I see automation credits for a specific client?

Yes — in the client card, in the operation history: bonus credits and debits by rules are recorded as automation operations.

About IZI