Skip to content

What runs automatically ​

A great deal of Xperios happens without anybody pressing anything — invoices raised, pupils carried into the new year, reminders sent, offers closed off. When one of those has not happened, the first useful question is how often that particular thing runs, because the answer is not the same for all of them.

"Overnight" is only true of some of it

It is a reasonable shorthand for invoicing, and wrong for a good deal else. Progression runs roughly every eight hours, not once a night, and dashboard emails and ticket messages run every hour.

So "it will be there in the morning" is sound advice about an invoice and misleading about almost everything else.

Every hour ​

Dashboard emailsSent at the hour each person chose
The weekly business reportBuilt and sent on its schedule
Ticket emailsConfirmations, tickets, performance notices
Ticket holdsAn unpaid hold is released so the seats go back on sale

Roughly every eight hours ​

Three times a day, which changes what you should do about it: something you are waiting on may well appear within a few hours, so looking again later the same day is usually right, where "overnight" would have had you coming back tomorrow.

ProgressionPupils, group members, hires and school-billed hires carried into the new year
RemindersUnconfirmed lessons, SLA sign-off, consultation bookings, debtor reminders
Connection requestsTelling teachers that a parent has asked to be joined to a lesson
Query alertsChecking whether a query you are watching has rows in it
Scheduled reportsReports set to arrive on a timetable
Card reconciliationChecking what the payment providers actually took

Once a day ​

InvoicingBoth runs — parents and organisations
Card collectionPayment schedules collected
Offer remindersChasing tuition and hire offers nobody has answered
The tidy-upAuto-declines offers left open past their window, and clears away abandoned applications
Distribution listsDynamic lists rebuilt against who now matches them
The annual details checkAsking families to confirm their details
Anonymise requestsCarrying out requests that have been approved

Once a week ​

Register notificationsChasing registers that have not been marked
Absence notificationsThe absence warnings, where they are switched on
Unfulfilled diary creditsCrediting sessions that did not happen
Archiving and anonymisingThe retention housekeeping

What this means in practice ​

Nothing is instant, and fixing the cause does not reprocess the past. Put right whatever was blocking something and it is the next run that acts on it. Nothing goes back and picks up what an earlier run passed over.

Most of them do not report what they skipped ​

This is the single most useful thing to know about any of it. A run that has not happened yet and a run that considered your pupil and passed over them look exactly the same from outside — there is no list of what was left out, and nothing on the record says it was looked at.

It is not an oversight in one place; it is the normal shape. Progression skips a held payer and records nothing. Organisation invoicing skips a line it cannot price and records nothing. In each case the work was done, the decision was made, and the only trace is the absence of a result.

So the question to ask is never "has it run yet?" — it is "what about this record would make it refuse?" Waiting longer cannot tell those apart; looking at the record can. The how-to page for each area is written around that question, and the two commonest silent causes are a payer's account being held and a pupil having outgrown their school.

If something has not happened after a day, it is not timing. Work through the how-to for that area rather than waiting another night.

See also ​

Paritor - Winslade Park, Manor Drive, Clyst St Mary, EX5 1FY