Keeping values fresh

Last updated 2 September 2026.

Values reach Trivela three ways, for three kinds of change. Most services use the first two; a service whose values move while the player is elsewhere needs the third.

On render

Every link/status call you make to read can carry values. If you already call it when you draw the connection — and you should — then the player’s values are re-sent every time they open the page, at no extra cost. This is the baseline: nothing is ever more than one visit stale.

When the player changes something

The player edits something on your site that you feed to Trivela. Their next visit to your settings page is not soon enough when other services read the value — that window is days wide. Send right after the change, from a background task so the response is not slowed, and never let that push throw: a report that does not land is corrected by the next render or by the feed below.

When the value changes on its own

Some values move without the player doing anything on your site — a number that changes as they play, a record that updates overnight. For values like that, report everyone on a schedule with link/report:

POST /api/link/report
{ "reports": [ { "subject": "u_8f31c2", "values": { … } }, … ] }     ← up to 500 per call

200 { "service": "yourservice", "accepted": 412, "unknown": 9 }

Everyone linked, not just those who changed. Detecting “changed” needs a second copy of the truth whose staleness is silent. Re-sending an unchanged value is cheap.
Chunk at 500, and let a failed chunk not stop the ones after it. A partial run is reported as a partial run.
Once a day is enough. There is nothing to gain from more than a few times a day.
It returns counts only and reads nothing back — unknown is the number of subjects with no live link to you, never which ones.