Self-diagnosis for problems
First steps when the chatbot does not respond or a channel does not work.
Last verified: 2026-07-20
Before contacting Zentor, you can check a few things yourself to narrow down where a problem lies: dashboard system status, the test function of the affected channel, and the action log.
Step by step
- Check the system status on the dashboardOn the home page ("Dashboard"), a panel shows the status of API, database, n8n, and Redis. If a row is not "OK", the cause may lie there.
- Test the affected channelIn the "Integrations" section, there is a "Test" button for email, Telegram, and WhatsApp that actively verifies the connection.
- Review the action logIn the "Logs" section you see a log of recent actions (timestamp, action, affected entity, acting user) — helpful to understand what was last changed.
- For automations: check workflow runsIn the "Automation" section, on the "Runs" tab, you see the status (success/failed/running), start time, and duration of individual automation runs.
Expected result
You can narrow down the rough source of the error (system, channel connection, or automation step) before contacting Zentor.
Common error cases
I cannot find a targeted filter function (e.g. by date or module) in the Logs section.
Cause: The Logs section currently shows the most recent entries without a filter interface in the dashboard.
Resolution: Browse the displayed entries manually; for targeted analysis, contact Zentor.
An automation run failed, but I cannot find a detail view or a retry option.
Cause: The status of individual runs is visible, but a detail/error view as well as a "retry" button are not currently available in the dashboard.
Resolution: Note the time and affected workflow and contact Zentor.
I want to trace failed email deliveries in detail.
Cause: A detailed dispatch log exists but is only accessible to Zentor (Master Admin), not in the tenant dashboard.
Resolution: Contact Zentor with the affected email details (recipient, approximate time).