Help center support eXpress

We've collected answers to popular questions to make eXpress easy and convenient to use. Didn't find the answer to your question? Contact our support team.

Bots & SmartApps Logs
Updated 8 Oct 2026

Bots & SmartApps Logs

Client-side logs are collected from the user's device; server-side logs are collected from the infrastructure where the bot or SmartApp is hosted.

Bots & SmartApps Client Logs

CTS
eCTS
⚠️ For Administrators: before reproducing the issue and collecting client logs for a SmartApp, you may need to enable debug variables on the server side first — more details.

Collecting SmartApp Logs Without the Engineering Menu

You can collect a SmartApp log and send it to support directly from the app menu — the ellipsis button in the open SmartApp. The engineering menu is not required. The available commands depend on how the administrator configured the SmartApp:

    How the administrator configured the SmartApp How to collect and send the log
    A separate support app is assigned Tap Contact Support: the command opens the support app and passes it an archive with the log. The log is written from the moment the SmartApp opens. A screenshot is attached to the log if the administrator has enabled it and screenshots are allowed in your organization. There is no separate command to export the log in this case.
    No support app; continuous log recording is enabled Tap Share logs: the log is exported to you. Attach it to your support request yourself.
    Continuous log recording is disabled Enable recording manually: tap Start collecting logs, reproduce the issue, and tap Stop logging and download (web and desktop) or Stop Log Collection (Android and iOS).
Available in the server software, web/desktop app and on iOS starting from version 3.72, and on Android starting from version 3.73. If you need a log from the very start of SmartApp while continuous recording is off, see “SmartApp Log Since Launch”.

Collecting Bots & SmartApps Client Logs via “About” Screen

Bots and SmartApps logs are available via “About” Screen.

For bot diagnostics, client logs are not enough: server logs are also required.

SmartApp Log Since Launch

It is needed if an error occurs immediately when opening SmartApp and collecting the log via the ellipsis is not possible. There are two ways:

  • Ask your organization's server administrator to enable Persistent log recording for this SmartApp in the “Bots” section. The log will be written each time SmartApp opens: reproduce the error and export the log using the ellipsis button.
  • If the administrator is unavailable, collect diagnostics through the “About” screen: Settings > About > Start Log Collection (web and desktop) or Start collecting diagnostic information (Android and iOS), open SmartApp and wait 15 seconds, then About > Stop and share.

Server Logs for Bots & SmartApps

CTS
eCTS
The instructions below are for standard eXpress bots in containers. Logs from third-party bots may be collected differently: to learn how to collect diagnostics for such a bot, ask its developer.
For Administrators: Debug Settings for Bots/SmartApps
  1. If necessary, change the debug variables in the file /opt/express/bots/your_bot/.env and restart the bot/SmartApp and Worker containers.
    ⚠️ Debug variables are not available in all bots and SmartApps.
    Debug Variable What it enables
    DEBUG=true|false Enables verbose logging for the main bot or SmartApp components.
    IMAP_DEBUG=true|false Only for Email SmartApp: enables verbose logging for the IMAP client. Also requires DEBUG=true.
    EXCHANGE_DEBUG=true|false Only for Email/Calendar SmartApps: enables verbose logging for the Exchange client. Also requires DEBUG=true.
For Administrators: Collecting Server Logs for Bots/SmartApps
  1. Connect to server for collecting logs. Identify bot/SmartApp container name (last column): docker ps
    Some SmartApps might have two containers (main and worker). In such cases, logs from both SmartApp containers are required.
  2. Export logs: docker logs CONTAINER_NAME > /tmp/bot_logs.txt 2>&1
  3. Download the file: scp user@your.server:/tmp/bot_logs.txt
For Administrators: .env & docker-compose.yaml Files
  1. If support requests it, send them the /opt/express/bots/your_bot/.env file and the docker-compose.yaml configuration file from /opt/express/bots/your_bot/. Before sending, remove sensitive data from the .env file.

Related questions