System Log Codes Reference
Every operational log code emitted by the BizKitHub core — the identifiers you see in subject lines of technical-notification e-mails (such as TTL_003 or INTERNAL_FIO_API_UNAVAILABLE) and as code badges in the admin log viewer. Unlike API error codes, these never reach external clients; they describe background events, integrations, and cron-driven workflows.
They are registered automatically the first time the core emits one via writeLog(). The platform team curates each code with a human-readable title and a short description so operators can understand the e-mail subject at a glance.
Common (fallback) error
Fallback code assigned by the logging layer (`resolveLogMessage()`) when an entry is written without an explicit `code`. The actual root cause lives in the log message body; high counts here usually mean the caller should emit a specific dedicated code instead.
Cron job failure (legacy)
Legacy code from an earlier cron runner. No longer emitted by current source; historical entries are kept for audit purposes only.
Manual e-mail has been sent
Audit entry written when an operator dispatches a manual e-mail (newsletter, segmented broadcast or one-off message) via `composeMail()`. Informational — no action required.
E-mail dispatch failed
An exception was raised during `composeMail()` while preparing or handing off the message to the SMTP/queue layer. The recipient was not reached; inspect the message body for the upstream error.
SMTP configuration test succeeded
Written after a successful test send through a newly-saved SMTP configuration. Confirms host, port and credentials are working.
SMTP configuration test failed
The saved SMTP configuration could not deliver the test message. Verify host/port, credentials and that the provider permits sending from the configured From address.
Fio bank sync warning (legacy)
Legacy Fio bank integration code. Replaced by the `INTERNAL_FIO_*` family; no longer emitted by current source.
Fio bank sync failure (legacy)
Legacy Fio bank integration code. Replaced by the `INTERNAL_FIO_*` family; no longer emitted by current source.
No payment gateway configured
An order tried to create an online payment but no gateway (Comgate / Stripe / GoPay …) is configured for the organisation or its order group. The customer cannot pay online until a gateway is set up in the admin.
Online payment creation failed
The payment provider rejected the create-payment request (provider API error, wrong credentials or malformed payload). The customer was not redirected to the payment screen — inspect the message body for the provider response.
Payment gateway error (reserved)
Reserved gateway code from an earlier integration. Never emitted by current source.
Fio bank API unavailable
Stored as the 16-character truncation of `INTERNAL_FIO_API_UNAVAILABLE`. The Fio bank API did not respond in time or returned a malformed body during the periodic statement sync. Usually transient (Fio downtime or network blip) and resolves on the next cron tick; persistent occurrences indicate a real Fio outage.
Fio bank API token inactive
Stored as the 16-character truncation of `INTERNAL_FIO_TOKEN_INACTIVE`. Fio API returned a token-rejected error during statement sync — the configured API token has been revoked, expired or was never activated in Fio internet banking. Generate a fresh token and update the bank account configuration.
TTLock API: operation failed (code 1)
TTLock cloud API rejected the operation with the generic error code 1 ("failed / means no"). Often returned when the lock cannot acknowledge the request — check gateway connectivity and lock health.
TTLock API: error 10004
TTLock cloud API returned error 10004 (request validation failure). Inspect the message body for the offending parameter.
TTLock API: device not connected to a gateway
TTLock API reports that the lock has no associated gateway (code 2012). Either the gateway is unplugged/offline or the lock has been unpaired in the TTLock app.
TTLock API: gateway offline
TTLock API reports the gateway as offline (code 3002). Same condition as `TTL_003` but raised from a per-operation API call rather than the periodic healthcheck cron.
TTLock API: gateway busy
TTLock API reports the gateway as busy (code 3003) — another command is already in flight on the same gateway. Transient; the operation queue retries automatically.
TTLock API: remote command timed out
TTLock API code 3009 — the gateway acknowledged the request but did not confirm completion within the timeout window. Usually transient and retried by the queue.
TTLock API: unknown error
TTLock cloud API returned an error response without a recognised numeric code. Inspect the message body — most often a transport-level failure rather than a real lock issue.
TTLock passcode provisioning failed
Adding a passcode to a smart lock failed while provisioning access for a calendar event. If a backup code was used as fallback the entry is logged at `error`; if no usable backup exists the entry is `critical` with an e-mail — the guest cannot enter and an operator must intervene.
Unable to generate a unique passcode
After 50 attempts the password generator could not produce a code that does not collide with an existing active password on the lock. Indicates either DB drift or a lock with an unusually high number of active codes — investigate manually in the TTLock dashboard.
TTLock gateway is offline
The TTLock healthcheck detected that a lock's gateway transitioned from online to offline. The notification e-mail fires only when no working backup code is in place (or the backup expires within 3 days); otherwise the event is logged at `error` without notification.
TTLock gateway reconnected
A previously offline lock is reachable again and the rolling backup passcode has been refreshed. The recovery e-mail is sent only when the outage lasted at least 24 hours; shorter hiccups are logged at `info` without notification.
Lock battery level is critical
A lock reported its battery level at or below 25 %. Replace the batteries soon — once the lock loses power, all passcodes (including the backup) stop working until the batteries are replaced.
Common lock error (reserved)
Reserved generic lock-error code. Not currently emitted by any code path — kept for forward compatibility.
TTLock queue item exhausted retries
A queued lock operation has failed permanently after 10 retries (or was marked dead immediately for a non-retryable error). The API call will not be retried further; inspect the entry in the TTLock queue dashboard to see which operation was abandoned.
Severity scale
Each code is emitted at one of five severity levels at runtime. A critical-level occurrence triggers a notification e-mail to the organisation's support address; lower levels are recorded in the admin log viewer but do not send mail.
Routine activity
Healthy outcome
Logged failure
Needs attention
Notification sent