Skip to content

Decisions

How data age works

A decision chooses what a screen shows from your data. If that data stops arriving, the decision would go on choosing from old values: yesterday’s price, or an item that has since sold out. So every decision has a data age limit. Whoever makes the decision live chooses it. Mestra never chooses it for you.

Choosing the limit

When you make a decision live, you say how old its data may be, from 1 minute to 7 days. Nothing is filled in for you. You can change it later on the decision’s page, under Data may be up to… > Change.

How the age is counted

The age is the time since Mestra last confirmed the data with where it comes from.

  • For a connector that Mestra fetches on a schedule, it is the last successful check. A check that finds nothing has changed still counts, because Mestra asked and got an answer.
  • For a connector your system sends to, or an upload, it is when the data last arrived. If what you send says when it was taken, that earlier time is used.
  • A full snapshot confirms the whole table. To send one, set the connector’s route to Replace everything and send the whole list each time. Rows that are not in it are removed. If a row in the snapshot was refused, or rows that are gone could not be removed, the table is not confirmed as a whole until a clean snapshot arrives. (If that same connector also adds and updates rows in that table, the rows the snapshot did accept are still confirmed.)
  • An arrival that adds and updates rows (Add and update) confirms only the rows in it. A row that is not in the arrival keeps the age it had. A row that was refused is not confirmed either, and keeps its age. The other rows in the same arrival are confirmed.
  • A row that is sent again unchanged is confirmed, so a row you send every minute never grows old. The exceptions are a row that another connector also sends and has confirmed later, and a row whose last arrival said its data was taken later than this one says.
  • If your system sends only what changed, rows that do not change grow old. A screen shows the default row when any row at its place, in a table the decision reads, is too old, even a row the decision did not use. So one item your system stopped sending (discontinued, but never deleted) keeps every screen at that place on the default row, for decisions that read that table, until a full snapshot removes it. To avoid this, send the full list on a schedule shorter than your limit, or include unchanged rows each time. When you stop sending an item, remove it with a full snapshot.
  • Adding and updating never removes a row.
  • An arrival says nothing about a table it did not cover. Sales arriving every minute say nothing about a menu table sent once a day.
  • If a decision reads several tables, the oldest one counts.
  • If several connectors feed one table, the one that confirmed it longest ago counts. A connector that feeds a table but has never sent anything (one added and never set up, for example) keeps that table old until it sends or you stop it feeding that table.
  • Data with no connector or feed behind it, such as facts about the screen itself, never counts as old.

The age keeps counting while a connector is failing, and while a screen has no connection.

What a screen shows when the data is too old

The screen shows the campaign’s default row until fresh data arrives. Then it goes back to what the decision chooses. Nothing is blank and nothing needs restarting.

Screens with no connection

A screen that goes offline keeps following the decision on its own clock, but only until the data it was last sent reaches the limit. After that it shows the default row until it reconnects. So the limit you choose is also the longest a disconnected screen will keep following the decision.

Choosing a limit that leaves no gaps

A limit shorter than how often your data is renewed means screens will spend part of the time on the default row. If a connector checks every 5 minutes, a limit of a few minutes will leave gaps. The dialog shows the shortest limit that leaves none, when Mestra can work it out. For data your own system sends, Mestra cannot know how often it will arrive, so it gives no figure.

Seeing it

A decision’s page shows when its data was last checked and by which connector. It also says when screens are on the default row because the data is too old, and how many rows have not been sent again within the limit.

Topos home lists decisions whose data is too old, and decisions that are live with no limit chosen. Those show the default row until someone chooses one.