Skip to content

Decisions

Test, go live and read the log

This page covers what you do with a decision after you save it. See Decisions to write one.

Test

The Test section of a decision’s page runs the source in the editor, saved or not, and shows what it would choose. It stores nothing: no version, no log entry. Only owners can test.

  1. Screen. Choose a screen from the list, or No screen. The list shows the screens of your connected screen systems. With No screen, the time is read in UTC and there is no place.
  2. Time (optional). Pick a date and time in your browser’s time zone. Blank is now.
  3. Select Run test.

The result shows:

  • Row chosen, with its label, and “(the default row)” if it is the default. Or “No row can be shown.”
  • Reasons, the text you gave show.
  • If it failed, “It fell back to the default row:” and the reason, such as “it took too many steps”. In your own test, a short message with the real cause also shows.
  • What the decision saw, a tree of ctx: the time, the screen, the signals, the place, the items and the rows. Use it to see why a decision chose what it did.

A test needs the campaign to have approved rules and a saved table. Otherwise it says “Approve the rules first” or “Save the table first”. If the source can’t be read, the message is “Line N: …”. If what the screen can see is too large, it says “What this screen can see is too large for a decision to read.” A screen that isn’t in your last screen read says “That screen isn’t in your last screen read.”

Versions

Versions lists every version, newest first. Each shows its state:

State Meaning
Saved (with the time) Saved and not live.
Live The one screens follow for this campaign.
Replaced It was live, and a newer version was made live.
Taken down (with the time) It was live and an owner took it down.

Select View to load a version’s source into the editor. The editor shows which version is open.

Make a version live

  1. Select Make live on a saved version.
  2. Confirm “Make version N live? Screens will follow it from now on.”

Mestra says “Version N is live.” A campaign has one live version. Making another live replaces the earlier one, which becomes Replaced. The page then says how many screens the decision decides for and when it last changed one: “Decides for 12 screens. Last change 14 Nov 2026, 9:30 am.”

A version that is already live, was taken down or was replaced can’t be made live again. Mestra says “That version can’t be made live: it is already live, or it was taken down or replaced.” To go live again, change the source and save a new version.

Take a version down

  1. Select Take down on the live version.
  2. Confirm “Take version N down? Screens go back to the table.”

Mestra says “Version N is taken down.” Screens go back to the campaign’s table. If the version you try to take down isn’t live, Mestra says “That version isn’t the one screens follow, so there is nothing to take down.”

Making a version live or taking it down is recorded in Recent activity on the home page, with who did it.

The log

Log lists what each screen was shown for the decision’s campaign, newest first, 50 at a time. Select Show more for more. A new entry is written when what a screen is shown changes: the row, a failure or the version. Each entry shows:

  • the row chosen, or “No row”,
  • when, the screen, and the version,
  • “default” if the default row was chosen.

The log holds the version that decided and the scope it read, so it can be replayed.

Replay a logged decision

Select Replay on a log entry. Anyone in the organisation can do this. Mestra runs the same version again over the same scope and says:

  • Same result, if it gives the row that was recorded.
  • “Different result: ” and the row, if it doesn’t.
  • “That decision is no longer kept.” if the entry is gone.

A replay uses the version and data the decision saw at the time. A newer version, a table that has changed or an archived item doesn’t change the answer. A replay stores nothing.

Taking it back

If a live decision does the wrong thing, take it down. The table answers at once. Fix the source, save a new version, test it and make that live.