Scheduled jobs
Some work happens on its own, without anyone pressing a button: working out late-payment penalties and arrears each night, tracking missed Savings Club contributions, checking whether goals have matured, crediting monthly savings interest and charging monthly account maintenance fees. The Scheduled Jobs screen shows whether each of these ran and how each run went.
Who can use it: the platform operator only. The jobs run for every organisation at once, so the screen is not shown to an organisation's Admins or Proprietor. If a job looks wrong for your organisation, ask the platform operator.
Opening the screen
The platform operator selects Scheduled Jobs under Administration in the left-hand menu. The jobs are grouped by product (Small Loans, Savings Club and the platform's own jobs). The times shown are in the time zone printed under the heading. The screen refreshes itself every minute.
Each job shows:
- its name, a coloured dot and its state;
- when it is scheduled to run, and what it does;
- the last run: when it started, how long it took and what it handled (the figures that are not zero);
- Overdue if no run starts by: the time after which a missing run counts as overdue;
- if the last run failed, the end of its error message;
- a strip of the last 25 runs, oldest on the left. Hover over a run for its details.
What the states mean
| State | Shown as | Meaning |
|---|---|---|
| Succeeded | green | The latest run finished normally. |
| Running now | blue | A run has started and not yet finished. |
| No runs yet | grey | The job has never run. |
| Some tenants failed | orange | The run finished, but it skipped one or more organisations because of an error. Those organisations were left unchanged. |
| Failed | red | The latest run failed, or stopped part-way (for example the system restarted during it). |
| Overdue | red | The job should have started by now and has not. |
A warning at the top of the screen appears while any job is overdue, failed or partly failed.
Alerts
When a run fails or skips an organisation, the platform emails the addresses its operator has set up for job alerts. If none are set up, the failure is only shown on this screen. A job that never starts cannot report itself, so overdue jobs are not emailed; the operator watches for them with an uptime check instead.
A job that failed stays red until it next succeeds. Once the cause is fixed, the platform operator re-runs it by hand for the missed day; the screen then shows the new run.
For what each job does, see Small loans and Savings.