Skip to content

Alerts catalogue

A Lucky Touch alert is not a message sent once: it describes a state of the venue. It appears when the state occurs and clears by itself when it is fixed. Acknowledging an alert says “seen” (with a reason if the venue requires one): the alert stays as long as the cause remains, and the acknowledgement only lasts a while (setting Validité d’un acquittement). See Alerts for the screen. Menu paths are quoted in French, as the back office shows them.

  • Who sees it: Operations = administrator, operations and supervisors; Registers = main register and tablet (register banner); Finance = money alerts; Security = floor alerts — “no amounts”: the sentence names neither an amount nor a register.
  • Severity: Critical needs action right away; Warning is to be handled; Information is for reading.
Alert Severity Who sees it It clears when
Device offline Critical Operations, Registers, Security The device talks to the server again.
Machine silent (the device no longer hears it) Critical Operations, Registers, Security The machine answers the device again (check the cable).
The machine does not hear the device Warning Operations, Registers, Security The machine answers again (check the machine address).
Configuration refused by the device Warning Operations, Registers, Security The device accepts its configuration (fix the denomination or coin value on the machine record).
Device firmware anomaly Warning Operations, Registers, Security The device no longer reports it; tell the technician.
Meters silent Warning Operations, Registers, Security The device sends its meter readings again.
Manual payment in progress on a machine Information Operations, Finance, Registers, Security The manual payment is paid or cleared.
Lost device messages Information Operations, Registers, Security When the device no longer reports it.
Machine not registered for transfers Critical or warning Operations, Registers, Security The machine is registered (automatically, or by hand from its operator menu).
Pulse machine still locked after a paid payment Warning Operations, Registers, Security (no amounts) The reset is proven (resent, or done by hand on the machine).
Pulse machine: events lost during an outage Information Operations, Registers, Security After the set delay (Paramètres → Réglages → Alertes).
Machine in test with a problem Warning Operations, Registers, Security The test is closed (test key turned).
Test closed without a reset Warning Operations, Registers, Security The reset is done on the machine.
No QR code on a machine waiting for a proof Warning Operations, Registers, Security The QR code is printed (machine record → « Imprimer le QR ») and the proof made.
Door open too long (Bally S5500) Warning Operations, Registers, Security The door is closed.
Alert Severity Who sees it It clears when
Device reading another machine Critical Operations, Registers, Security The replacement is confirmed or dismissed.
Two devices announce the same machine Warning Operations, Registers, Security One of them is adopted elsewhere or detached.
Device waiting for adoption Information Operations, Registers, Security The device is adopted (Exploitation → Boîtiers en attente).
Device card moved to another board Critical or warning Operations, Registers, Security Nothing clears it by itself: it stays until acknowledged (machine checked, suspended transfers decided), then clears when the acknowledgement expires.
Device board with a new card Critical or warning Operations, Registers, Security As above: until acknowledged, then when the acknowledgement expires.
Pulse machine: configuration not applied yet Warning Operations, Registers, Security The device announces the right profile; until then, no money order is sent.
Alert Severity Who sees it It clears when
Transfer pending or uncertain Critical or warning Operations, Finance, Registers, Security (no amounts) The transfer is completed or decided (Exploitation → Transferts).
Manual payment not paid Warning Operations, Finance, Registers, Security (no amounts) The manual payment is paid or cancelled.
Pulse machine: device meters disagree Critical Operations, Finance, Registers, Security (no amounts) The gap is checked and resolved; never corrected silently.
Pulse machine: uncertain coins Warning Operations, Finance, Registers, Security (no amounts) The coins are decided (refund or confirm).
Pulse machine: manual payment waiting Warning Operations, Finance, Registers, Security (no amounts) The amount is declared and the payment made.
Pulse manual payment to approve (implausible amount) Warning Operations, Finance, Registers, Security (no amounts) The payment is approved or refused.
New manual payment after a manual reset Critical Operations, Finance, Registers, Security (no amounts) Operations check the machine and confirm before any payment.
Uncertain player transfer (pulse machine) Critical Operations, Finance, Registers, Security (no amounts) The transfer is decided on the machine.
Over-committed intake Critical Operations, Finance, Registers The intake is regularised.
Debt open for a long time Warning Operations, Finance, Registers The debt is paid, credited or closed.
Tablet hand-in waiting Warning Operations, Finance, Registers The main register confirms or refuses the hand-in.
Tablet holding cash with no open register Warning Operations, Finance, Registers The tablet is linked to an open register and hands in its cash.
Tablet hand-in gap Warning Operations, Finance, Registers Operations regularise the gap.
Payment mode correction to approve Warning Operations, Finance The administrator approves or refuses the request.
Machine not measured for several days Warning Operations, Finance The machine meters are read; an acknowledgement lasts at most the set time.
General ledger: entry failed Critical Operations, Finance The entry is caught up or the item settled by the administrator.
General ledger: account missing from the posting scheme Warning Operations, Finance The scheme is completed (Comptabilité → Schéma).
General ledger: numbering late Warning Operations, Finance The entries receive their number.
General ledger: numbering failed Critical Operations, Finance Numbering resumes; otherwise, call the publisher.
General ledger: gap with the registers Warning Operations, Finance The gap is explained (Comptabilité → Contrôles).
General ledger: venue currency missing Warning Operations, Finance The currency is entered (Paramètres → Réglages → Salle).
General ledger: history takeover incomplete Critical Operations, Finance The items are written (new attempt every night).
General ledger: restore to check Critical Operations, Finance Call your technician or the publisher.
General ledger: numbering on hold Warning Operations, Finance At the next contact with the platform, or lifted by the administrator (Comptabilité → Contrôles).
Gaming day not closed Warning Operations, Finance The day is closed (Comptabilité → Clôtures).
Period archive missing Critical Operations, Finance The archive is rebuilt (Comptabilité → Clôtures → Archives).
Day closed despite an imbalance Critical Operations, Finance The imbalance is corrected by a manual journal entry.
Archive refused by the platform Critical Operations, Finance To check with the publisher.
Fiscal year start to correct Warning Operations, Finance The owner changes the fiscal year start (Comptabilité → Clôtures → Exercice).
Archives not yet received by the platform Warning Operations, Finance The archives are received; otherwise, check with the publisher.
General ledger: protection to check Critical Operations, Finance Call your technician or the publisher.
General ledger: change refused Critical Operations, Finance Call your technician or the publisher.
General ledger: integrity chain broken Critical Operations, Finance Checked (Comptabilité → Grand livre → Contrôles), then acknowledged; report it to the publisher.
General ledger: integrity check stopped Critical Operations, Finance The check resumes; otherwise, report it to the publisher.
General ledger: integrity verification late Warning Operations, Finance A full verification succeeds (« Vérifier la chaîne maintenant »).
General ledger: integrity check to verify Critical or critical or warning Operations, Finance Call your technician or the publisher.
Archive refused by the platform Critical Operations, Finance Call your technician or the publisher.
Waiting register floats with a gap Warning Operations, Finance The gap is explained (Comptabilité → Fonds et avoirs → Fonds en attente).
Register gap to decide Warning Operations, Finance The gap is decided (Comptabilité → Fonds et avoirs → Écarts de caisse).
Register ↔ meters gap to justify Warning Operations, Finance The gap is justified (Comptabilité → Fonds et avoirs → Caisse ↔ compteurs).
Suspense account not justified Warning Operations, Finance The amounts are justified (Comptabilité → Fonds et avoirs → Compte d’attente).
Loss declared although the money arrived elsewhere Critical Operations, Finance The loss is reversed (Coffre → Transferts entre salles).
Alert Severity Who sees it It clears when
Too much cash in a drawer Warning Operations, Finance, Registers The excess is dropped to the safe.
Register low Warning Operations, Finance, Registers At the next refill of the register.
Safe request (refill or drop) Information Operations, Finance, Registers The request is authorised or refused.
Refill auto-approved for lack of answer Information Operations, Finance For information: it clears with the day.
Register of a former company to close Warning Operations, Finance The register is closed.
Alert Severity Who sees it It clears when
Safe low Warning Operations, Finance The safe goes back above the threshold (top-up).
Safe count overdue Information Operations, Finance A safe count is confirmed.
Safe withdrawal to approve Warning Operations, Finance The administrator approves or refuses the withdrawal.
Transit loss waiting for the owner Warning Operations, Finance The owner decides it in the online back office (or the venue withdraws its request).
Alert Severity Who sees it It clears when
Email subscription failed Warning Operations, Finance The next sending succeeds.
Alert Severity Who sees it It clears when
Venue data inconsistent Critical Operations Call your technician or the publisher.
Venue identity to check Critical Operations Call your technician or the publisher.
PIN sign-in to check Critical Operations Call your technician or the publisher.
PIN sign-in to confirm Warning Operations Call your technician or the publisher.
Deferred exports impossible Warning Operations Call your technician or the publisher.
Sync to repair Critical Operations Call your technician or the publisher.
Sync stopped Critical Operations Call your technician or the publisher.
Venue stopped by the platform Critical Operations Call your technician or the publisher.
Sync queue too large Critical Operations Call your technician or the publisher.
Sync late Warning Operations The venue’s sendings are received by the platform again.
Venue clock off Warning Operations The venue PC’s time is set.
Audit log to check Depends Operations Call your technician or the publisher.
Emergency account to adopt by the company Warning Operations The account becomes a company person, or is disabled after the set delay.
PIN to reassign (company) Warning Operations The PIN is reassigned in the online back office.
Company people suspended in the venue Warning Operations When contact with the platform is back.
PIN sign-in of company people unavailable Critical Operations Call your technician or the publisher.
Platform link to check Critical or warning Operations Call your technician or the publisher.
Platform orders refused Critical Operations Call your technician or the publisher.
Secrets backup to do Warning Operations The secrets backup is downloaded (Paramètres → Plateforme → Sauvegarde des secrets).
Platform link to renew Critical Operations Call your technician or the publisher.
Update service silent Warning Operations The service answers again (restart the venue PC, otherwise call the technician).
Update rolled back (previous version restored) Warning Operations Some time after the rollback; no data lost.
Update failed Critical Operations Some time after the failure; call your technician.
Backups (late, failed, USB key not copied, never tested, disk, restore…) Critical or warning Operations The cause is fixed: a backup succeeds, a copy to a key is made, a test succeeds.
Register station left on the old version Warning Operations The station moves to the new version.
Too many new register stations for one account Warning Operations When the cause is fixed (see Paramètres → Postes de caisse).
Approval code blocked Warning Operations At the end of the block, or the administrator resets it.
Approval code to unblock Warning Operations The administrator resets it.