Fix a problem

Quick answers to the things that occasionally go wrong — and exactly what to send us if you need a hand.

Common fixes

Google says "Action needed"

• Check the Google connection is still valid in your dashboard.
• Make sure the services you switched on match what you're trying to do.
• Been more than seven days in Testing Mode? Run Reconnect Google to refresh it.

Telegram bot isn't replying

• Confirm the bot token hasn't been changed inside @BotFather without updating Console.
• Check the bot username in Console matches the token exactly.
• Run a Console delivery probe to test the connection.

Images missing in a document

This is usually an images-in-documents issue. Check the image format is supported (PNG, JPEG, or WEBP) and that your agent can read the folder it lives in.

Device stuck "not Ready"

• Re-run the companion installer steps from the Devices page.
• Confirm the host can reach the network paths Console documents for enrollment.
• Note the platform (macOS, Windows, Linux) and the last status message from the Devices card.

Contact support

When you open a ticket, include a support packet — a short list of non-sensitive details that lets us diagnose quickly. Copy the template below and fill it in.

- Page or integration: e.g. Google integration- Account or bot label:  e.g. workspace email / @my_bot- Console status:        e.g. Action needed / Connected- Scopes or channel:     e.g. Gmail + Calendar- Latest probe result:   e.g. failed at step 3 — timeout