Track interventions
Know who restarted a simulator, opened it, locked it, put it on standby or in maintenance, and when.
The Log page keeps a record of the interventions made on your simulators: restarts, unlocks and locks, standby, maintenance, free access. It is used to understand what happened to a simulator, and to know who did it.
What is logged
| Action | Where it comes from |
|---|---|
| Restart | Restart button on the Simulators page, or scan of a Restart command QR code. |
| Unlock | Lock column on the Simulators page, or scan of an Unlock command QR code. |
| Lock | Lock column on the Simulators page. |
| Standby on, Standby off | Standby column on the Simulators page. |
| Maintenance on, Maintenance off | Maint. button on the Simulators page, or scan of a Maintenance command QR code. |
| Free access | Scan of a Free access command QR code. |
| Free access on, Free access off | Free-access mode box ticked or unticked in the simulator settings (⚙). |
| Omnisim support | An intervention by Omnisim support on the simulator. |
Older rows sometimes show Maintenance alone, without the direction: they date from before the log recorded it.
Customer QR code scans do not appear in the log: see View sessions.
Find an intervention
Open the log
Open Log, in the Activity group of the sidebar. The interventions of the selected centers are shown, most recent first. A divider with the date separates each day; the rows themselves only show the time. On mobile, each card shows the full date and time.
captures/en/journal/listeLog page: list of interventions with their action, source, operator, simulator and statusFilter
- All actions: a single action.
- All sources: Admin for commands sent from NEXUS, QR Code for command QR codes scanned at the simulator, Simulator for settings changed on the simulator itself.
- Dates: from the first to the last day inclusive, in center days (midnight to midnight, center time). With several centers in different time zones, the first one's time is used, as shown on screen: "Dates in … time".
Read the row
| Column | What it shows |
|---|---|
| Time | The time of the intervention; the date is on the day's divider. |
| Action | What was done. |
| Source | Admin, QR Code or Simulator. |
| Operator | The email address of the NEXUS account behind the intervention. Empty for the Simulator source. |
| Simulator | The simulator concerned. |
| Center (details) | The simulator's center. |
| Status | Success, Failure followed by the error message returned by the simulator, or Scanned (see below). |
Result
Only the interventions that match your filters stay displayed, 30 per page.
Good to know
- A NEXUS command only appears once carried out. The row is written when the simulator has applied the command; a command sent to a simulator that never received it does not appear.
- A command QR code is recorded as soon as it is scanned, with the Scanned status. The row then changes to Success or Failure when the simulator has carried out the command, even if it was offline at that moment. A row that stays Scanned means that the simulator did not send back a result.
- For a command QR code, the operator is the person who created the QR code, not the person who scanned it: each scan adds a row in their name. Keep printed command QR codes out of the public's reach. See Issue a QR code from NEXUS.
Troubleshooting
| Symptom | Cause | Solution |
|---|---|---|
| "No intervention recorded" | No intervention logged for the period and centers chosen. | Widen the dates, or select other centers in the sidebar. |
| An expected intervention is missing | The simulator never received the command, or the action is not logged (scan of a customer ticket, maintenance ticked in the simulator settings). | Check the simulator's status in Simulators. |
| A row stays at the Scanned status | The simulator did not send back the result of the command QR code. | Check on the simulator that the command took effect; otherwise, scan the QR code again. |
| Clicking Log takes you back to Simulators | Your role does not give access to the log. | Ask an administrator of the account for access. |