Scheduled Tasks
Five Next Exams routines run in the background through Joomla's own Scheduled Tasks system. None of them are created for you, because Joomla scheduled tasks need a trigger strategy that only you can choose.
Nothing breaks without them — Next Exams sends its mail immediately when an event fires, and closes abandoned attempts opportunistically. What you lose is every retry and every time-based action.

The five routines
| Routine | What it does | Without it |
|---|---|---|
nextexams.notifications.flush |
Retries queued emails that failed their immediate send, and sends certificate issued emails that were waiting for results to be released | A failed email is never retried, and a waiting certificate email goes out only when an administrator next opens Attempts or the Live Monitor |
nextexams.webhooks.flush |
Retries queued webhook deliveries that failed | A failed delivery stays pending forever |
nextexams.certificates.sweep |
Expires certificates that have passed their validity and sends expiry reminders | Reminders are never sent at all |
nextexams.reports.run |
Builds and emails due analytics reports | Scheduled reports are never sent at all |
nextexams.attempts.sweep |
Closes attempts the examinee abandoned — see Auto-close — and runs the housekeeping below | Attempts still close and housekeeping still runs, but only while somebody has an admin page open |
The distinction in the last column matters, and it splits three ways:
- The two flush routines are safety nets for something that usually succeeds on the first attempt.
- Certificate reminders and scheduled reports have no immediate path at all, so with no task they simply never happen.
- The attempt sweep is the exception: it also runs opportunistically whenever an administrator loads the live monitoring board or the Attempts list, at most once a minute. On a site whose admin pages are opened regularly, it will keep up on its own. Create the task when nobody is watching the admin — an overnight exam window, or a site administered infrequently — because an abandoned attempt holds one of that learner's allowed attempts open until it closes.
Warning: if you configure expiry reminders or report schedules and never create the corresponding task, the interface will show them as configured and nothing will ever be sent. There is no warning about this in the interface.
Housekeeping
Three jobs keep promises about data and access, so they run on their own schedule rather than depending on any feature switch:
| Job | What it does |
|---|---|
| Held certificate emails | Sends certificate issued emails that were waiting for the result to be released |
| Access pass expiry | Marks access passes whose end has passed as expired, sending pass.expired, and sends the ending soon email to passes ending within 24 hours |
| Recording retention | Deletes speaking recordings older than Keep recordings for (days), and uploads that were never finished after a day |
They run in two places:
- Opportunistically, at most once a minute, whenever an administrator opens the Attempts list or the live monitoring board — the same moment the attempt sweep runs.
- From the
nextexams.attempts.sweeptask, when you have created it. A scheduled run has no visitor waiting on it, so it handles larger batches: 200 passes at a time instead of 50, and up to 200 recordings.
Housekeeping runs even when auto-close is switched off. Turning off Close abandoned attempts automatically stops attempts being closed; it does not keep an expired pass open, a recording past its retention, or a certificate email unsent. Each job runs separately, so one failing — logged to the com_nextexams category — never stops the others.
On a site where nobody opens the admin regularly, create the attempts task. Without it, a pass still stops admitting its holder at its end time — access is checked against the end time itself — but it is not marked expired, the pass.expired webhook and the ending soon email wait, and old recordings stay on disk until somebody next opens the Attempts list.
Creating a task
- Go to System → Scheduled Tasks and click New.
- Choose the routine from the list.
- Give the task a name and set its execution rule — an interval of an hour is a reasonable starting point for all of them.
- Save and publish it.
Repeat for each routine you need. A site using none of the optional features needs no tasks at all.
Making tasks actually run
A Joomla scheduled task only executes when something triggers Joomla's scheduler. Check System → Scheduled Tasks → Options for the trigger mode.
| Trigger | Behaviour |
|---|---|
| Lazy (web-request) | Runs when a visitor happens to load a page. Simple, but timing depends entirely on site traffic |
| Web cron / URL | An external service calls a URL on a schedule |
| Command-line cron | Your host's cron calls Joomla's CLI |
For anything time-sensitive — expiry reminders due on a particular day, a report expected every Monday morning — use a real cron rather than the lazy trigger. A quiet site can go hours without a page load, and the lazy scheduler cannot run a task nobody triggered.
Interaction with notifications and the App Manager
The first four routines ultimately send mail, so they inherit the notification configuration:
- With notifications disabled, or the Notifications app switched off, nothing is sent regardless of the tasks.
- Certificate reminders also need the Certificates app; report runs also need the Analytics app.
- A task whose app is switched off skips rather than failing, so a disabled app does not fill your logs with errors.
The attempt sweep is deliberately different. It is not tied to any app, because closing an abandoned attempt is part of grading rather than an optional feature — switching an app off should never leave attempts stranded and attempt caps quietly consumed. Its only switch is Settings → Taking → Close abandoned attempts automatically. It may still send the examinee an email, and that part does follow the notification configuration.
Checking that they work
- System → Scheduled Tasks shows each task's last run time and its outcome. A task that has never run is the first thing to check.
- Enable the
com_nextexamslog category in System → Global Configuration → Logging and look for failures from the routines. - For the flush routines specifically, the pending queue itself is the evidence — a webhook delivery stuck pending with attempts climbing shows the retry is running; one stuck at a single attempt shows it is not.
Access control
| Action | Required permission |
|---|---|
| Create and manage scheduled tasks | Joomla's own permissions — this is standard Joomla administration |
| Configure what the routines act on | The relevant Next Exams permission for that feature |
The routines run as system processes and are not subject to Next Exams role permissions.