When scores update
Last updated on
There is nothing to schedule. A background job checks every account every 30 minutes and recomputes it when:
- it has never been scored,
- one of its signals was raised, resolved, dismissed or edited since its last score, or
- its score is more than 24 hours old.
A failed Stripe payment or cancellation, or a customer email flagged angry or urgent, recomputes the account straight away.
Each recompute updates the health score (unless pinned), closes agent signals whose condition has cleared (next section), and recomputes all five journey tracks and the journey stage. Risk & Health always moves together with the score.
Once a day the same job also moves every account's credits pace forward (what it should have used by today grows even when no new usage arrives), and a Usage API sync or an allowance change recomputes the affected accounts' pace within seconds.
Note
Lost accounts are not recomputed. If you've just changed something and don't want to wait, use Recompute now in the account's health ring (the score and Risk & Health), or Recompute tracks on the account page (all five tracks; see the Journey chapter).