Errors and support
Error FAQ: what a message means and what to do about it
The most common panel and API messages with the cause, the fix and who resolves it.
Most messages have a simple workaround; if there is none, report a bug from the panel together with the identifier.
The list is generated from code (fluxcrm/faq_bledow.py), and the same set suggests fixes in the panel and in the support chat.
The panel asks you to sign in or answers 401
Response code: 401
Cause. The session expired (after days without activity, or after signing out on another device), or an integration uses a wrong API key.
What to do. Sign in again. For an integration, check the x-fluxcrm-klucz header and whether the key has expired in Settings, API keys.
Who resolves it: you.
Sign-in is blocked after several failed attempts
Response code: 429
Cause. The limit on failed sign-ins protects accounts from password guessing. The block applies to the IP address and lifts by itself.
What to do. Wait for the time in the Retry-After header (usually a few minutes). If it was not you trying to sign in, the owner can remotely sign out the session in Settings, Security.
Who resolves it: you.
The code from the authenticator app (TOTP) is rejected
Response code: 401
Cause. The code depends on the phone's clock. With a drifting clock or an old secret the code does not match.
What to do. Turn on automatic time on the phone and enter a fresh code. If it still fails, the owner turns the account's 2FA off and on in Settings, Team accounts. The owner can also use a passkey.
Who resolves it: the instance owner.
A message about no access to a module, or read-only access
Response code: 403
Cause. The account's role (custom or built-in: read-only, salesperson) does not allow this action.
What to do. Ask the owner to change the role in Settings, Roles. Settings, account and key actions are performed only by the owner.
Who resolves it: the instance owner.
The feature is turned off in this instance
Response code: 403
Cause. Optional features (marketing, call alerts, AI agents and so on) are turned off per instance by the instance.toml file or by a flag.
What to do. The owner checks the state in GET /api/funkcje and turns the feature on with a flag, or removes it from the wylaczone (disabled) list in instance.toml.
Who resolves it: the instance owner.
Too many requests: slow down
Response code: 429
Cause. Request limits per minute protect the instance from a loop in an integration or a script.
What to do. Wait for Retry-After seconds. The integration should reduce its rate; the owner changes the limits in Settings, Security.
Who resolves it: the instance owner.
The panel is read-only (emergency mode)
Response code: 503
Cause. The owner or an automation turned on emergency mode, for example while a backup is being restored or the database has failed.
What to do. Read data as usual, changes will wait. The owner turns the mode off in Settings, Diagnostics, once the cause is gone.
Who resolves it: the instance owner.
A server error with an identifier (error id)
Response code: 500
Cause. An unexpected exception on the server side. Each one has an identifier, and the error log stores the details (without personal data).
What to do. Click Report a bug in the panel (a screenshot and the identifier are attached) or give the identifier to support. The owner sees the error in GET /api/bledy_serwera?id=...
Who resolves it: FluxLab support.
The database is unavailable or busy
Response code: 503
Cause. A long write (an import, a backup) or a disk problem. The instance retries the operation, so it usually passes within a dozen seconds.
What to do. Wait and try again. If the message keeps coming back, the owner checks Diagnostics (disk space, backups) and reports the case as critical.
Who resolves it: FluxLab support.
The form rejects the data (422 invalid fields)
Response code: 422
Cause. The server checked the fields and found an error (a wrong format, an empty required value, too long a text).
What to do. The response names the fields under the pola key. Fix them and save again; no data has been changed.
Who resolves it: you.
Mail does not reach the CRM
Cause. Most often an expired mailbox app password, a changed mail password, IMAP turned off, or an expired Google token (an app in test mode drops the token every 7 days).
What to do. Check Settings, Sources: the state of the last import. Fix the app password or connect Gmail again. The import starts by itself within a dozen minutes; the owner gets a notification about an import error.
Who resolves it: the instance owner.
Mail from the CRM does not arrive or lands in spam
Cause. Missing SPF, DKIM or DMARC records for the domain, a wrong SMTP password, or an address bounced by the recipient's server.
What to do. The owner runs the check in Settings, Mail, Deliverability: the report shows missing records and bounces. Addresses with a hard bounce go on the block list.
Who resolves it: the instance owner.
Dzwonek on the advisor's phone does not ring
Cause. On-call duty is off, there is no consent for notifications, the advisor is outside working hours or has an absence entered, or the call alert feature is turned off.
What to do. In the Dzwonek app check on-call duty and the notification consent. The owner sees the app's health and can order a phone diagnostic in the Support window.
Who resolves it: the instance owner.
The form on the website does not create opportunities
Response code: 401
Cause. A wrong or changed form secret, an inactive formularz source, or the browser rejected the request because of the origin.
What to do. Compare the secret on the website with the instance's secret file, check zrodla in instancja.toml and dozwolone_originy. Guide: form.
Who resolves it: the instance owner.
An account cannot be added: plan limit
Response code: 409
Cause. The instance's plan limits the number of active accounts (Pilot 3, Ready CRM 25, With integrations 200), or the licence has expired.
What to do. Turn off an unused account or move to a higher plan. FluxLab renews an expired licence.
Who resolves it: the instance owner.
The backup restore test ended with an error
Cause. No disk space, a damaged backup file, or a changed backup directory.
What to do. The owner checks Diagnostics, Backups. The case is critical, because without a working backup there is no RPO: report it at once.
Who resolves it: FluxLab support.
AI features do not respond
Cause. AI is off by default (ADR 0006), the model key is missing, or the provider is briefly unavailable. Without AI the rest of the panel works normally.
What to do. The owner turns AI on and enters the key in Settings. When the provider does not respond, the panel shows the version without AI, and the tasks return after a retry.
Who resolves it: the instance owner.
The panel shows old data or an old look after an update
Cause. The browser keeps the previous version of the panel in its cache (Service Worker).
What to do. Refresh the page twice (Ctrl+Shift+R). An app installed on the phone updates after it is closed and opened again.
Who resolves it: you.