Watchtower Control Room

Somchai Telegram Bot

Monitor connected apps, review incidents, onboard new projects, and keep your operational contract in one calm place.

Add Project Integration Guide
production

Somchai Telegram Bot

Healthy

http://100.67.241.67:18080/health

Container Pattern
somchai-bot
Source
Manual
Container
Waiting
Last Alert
None yet
Open Errors
0
Open Warnings
0
Info Events
0
Monitoring
Active
Edit project Implementation guide
Health

Endpoint Snapshot

LIVE

http://100.67.241.67:18080/health

Healthy
Status Code
200
Response Time
25 ms
Failures
0

Last checked: 2026-07-17 09:13:29 UTC

Recent Alerts

Somchai Telegram Bot Incident Feed

Somchai Telegram Bot · Log

1 log error(s) detected

Error
* **Root Cause**: The Telegram API is returning an `HTTP 409 Conflict` error. This specific error indicates that more than one instance of the bot is running simultaneously with the same API token and trying to fetch updates using the long polling method (`getUpdates`). * **Explanation**: Imagine your bot has a single, dedicated phone line to Telegram to listen for new messages. This error means a second copy of your bot tried to use that same phone line…
Status: Recorded Occurrences: 1 Last seen: 2026-07-02 02:26:33 UTC
View full analysis
* **Root Cause**: The Telegram API is returning an `HTTP 409 Conflict` error. This specific error indicates that more than one instance of the bot is running simultaneously with the same API token and trying to fetch updates using the long polling method (`getUpdates`). * **Explanation**: Imagine your bot has a single, dedicated phone line to Telegram to listen for new messages. This error means a second copy of your bot tried to use that same phone line while the first one was already listening, causing a conflict. Telegram only allows one listener at a time per bot token. * **Potential Fixes / Investigation**: * Search for and terminate any duplicate running instances of the bot application on your servers or container orchestrator (e.g., Docker, Kubernetes). * Review your deployment process to ensure it always stops the old version of the bot before starting a new one. * If the bot is in a crash-restart loop, the old connection may not have timed out before the new instance starts. Investigate the root cause of any crashes. * **Severity**: **HIGH**. The bot is unable to receive new messages from users, breaking its core functionality.
View raw incident details 
Fingerprint: 6844dc4ad07b
Occurrences: 1

2026-07-02T02:25:19.798982707Z bot loop error: 409 Client Error: Conflict for url: https://api.telegram.org/bot8909163788:AAHpzd7ixmIBR2FMD4BjXIEYy_pwkqk1gG8/getUpdates
Somchai Telegram Bot · Health

Live health recovered

Info
Live endpoint recovered for Somchai Telegram Bot
Status: Resolved Occurrences: 1 Last seen: 2026-06-23 06:12:10 UTC
View raw incident details 
Project: Somchai Telegram Bot
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: 200
Response time: 24ms
Recovered at: 2026-06-23T06:12:10.479658+00:00
Response: {"ok":true,"service":"somchai-api","db":"ok","qdrant":"ok","mode":"isolated-vps-station-manager"}
Somchai Telegram Bot · Health

Live health check failed

Info
Live endpoint is failing for Somchai Telegram Bot
Status: Resolved Occurrences: 1 Last seen: 2026-06-23 06:12:10 UTC
View raw incident details 
Project: Somchai Telegram Bot
Domain: 100.67.241.67
Endpoint: Live
URL: http://100.67.241.67:18080/health
Status: no response
Response time: 10751ms
Consecutive failures: 2
Checked at: 2026-06-23T06:03:04.719827+00:00
Somchai Telegram Bot · Log

1 log error(s) detected

Error
### Error 1 * **Root Cause**: The `Somchai Telegram Bot` sent a request to its backend service (`somchai-api`) that the service could not understand or process, resulting in an HTTP `400 Bad Request` error. This is a client-side error, meaning the problem originates from the bot's request. * **Explanation**: The Telegram bot tried to send information to another part of the system, but the information was malformed, incomplete, or in the wrong format. The…
Status: Recorded Occurrences: 1 Last seen: 2026-06-15 05:00:51 UTC
View full analysis
### Error 1 * **Root Cause**: The `Somchai Telegram Bot` sent a request to its backend service (`somchai-api`) that the service could not understand or process, resulting in an HTTP `400 Bad Request` error. This is a client-side error, meaning the problem originates from the bot's request. * **Explanation**: The Telegram bot tried to send information to another part of the system, but the information was malformed, incomplete, or in the wrong format. The receiving system rejected it because it couldn't make sense of the request. * **Investigation**: * Check the logs for the `somchai-api` container around the same timestamp (`04:59:44`) for a more detailed error message explaining *why* the request was bad (e.g., "missing field 'user_id'"). * Review recent code changes in the Telegram bot that might have altered the data sent to the `/v1/runs` endpoint. * Confirm that the bot is sending data that matches the API's requirements (the API contract). * **Severity**: **HIGH**. This error occurs in a "bot loop," suggesting a core, repeating function is failing. This likely breaks a key feature for users interacting with the bot.
View raw incident details 
Fingerprint: 0c696fea69e3
Occurrences: 1

2026-06-15T04:59:44.603319021Z bot loop error: 400 Client Error: Bad Request for url: http://somchai-api:8080/v1/runs
Somchai Telegram Bot · Log

1 log error(s) detected

Error
**Error 1: Telegram API Unauthorized** * **Root Cause:** The application is attempting to connect to the Telegram Bot API using an API token that is invalid, has been revoked, or has expired. The Telegram server is responding with a `401 Unauthorized` error, rejecting the connection. * **Explanation:** Think of the API token as the bot's password to access Telegram's services. Telegram is saying the password provided is wrong. Because of this, the bot can…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:46:38 UTC
View full analysis
**Error 1: Telegram API Unauthorized** * **Root Cause:** The application is attempting to connect to the Telegram Bot API using an API token that is invalid, has been revoked, or has expired. The Telegram server is responding with a `401 Unauthorized` error, rejecting the connection. * **Explanation:** Think of the API token as the bot's password to access Telegram's services. Telegram is saying the password provided is wrong. Because of this, the bot cannot log in to check for new messages from users. * **Potential Fixes:** * Verify that the Telegram API token used by the application is correct. Check your environment variables or configuration files (e.g., `.env`, `docker-compose.yml`). * The token may have been revoked. Go to the 'BotFather' chat in Telegram, select your bot, and generate a new API token. * Update your application's configuration with the new, correct token and redeploy the service. * **Severity:** **CRITICAL**. The bot's core functionality—receiving messages from Telegram—is completely broken. The application is effectively offline from a user's perspective.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 7

2026-06-14T02:45:49.092817713Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates
Somchai Telegram Bot · Log

1 log error(s) detected

Error
### **Error 1: Telegram API Unauthorized** * **Root Cause:** The application is providing an invalid or revoked API token when trying to communicate with the Telegram service. The `401 Client Error: Unauthorized` response from Telegram's server confirms an authentication failure. * **What Went Wrong (Simple Terms):** The application is trying to log into Telegram to check for new messages, but Telegram rejected its password (the API token). This is likely…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:41:27 UTC
View full analysis
### **Error 1: Telegram API Unauthorized** * **Root Cause:** The application is providing an invalid or revoked API token when trying to communicate with the Telegram service. The `401 Client Error: Unauthorized` response from Telegram's server confirms an authentication failure. * **What Went Wrong (Simple Terms):** The application is trying to log into Telegram to check for new messages, but Telegram rejected its password (the API token). This is likely because the token is incorrect, has expired, or was canceled. * **How to Fix:** 1. Check the application's configuration (e.g., environment variables, secrets management) to ensure the `TELEGRAM_BOT_TOKEN` is correct. 2. If the token appears correct, it may have been revoked. Use the `@BotFather` on Telegram to generate a new API token and update the application's configuration with the new value. * **Severity:** **CRITICAL**. The bot is completely unable to receive messages or perform any of its core functions.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 6

2026-06-14T02:40:49.987470090Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates
Somchai Telegram Bot · Log

1 log error(s) detected

Error
Here is the error analysis for 'Somchai Telegram Bot'. ### Error: Unauthorized API Access * **Root Cause:** The application is making a request to the Telegram Bot API using an invalid or revoked API token. The Telegram server is rejecting the request with a `401 Unauthorized` error. * **Simple Explanation:** The bot is trying to connect to Telegram's servers, but the "password" (API token) it's using is incorrect. Telegram doesn't recognize the bot, so i…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:36:18 UTC
View full analysis
Here is the error analysis for 'Somchai Telegram Bot'. ### Error: Unauthorized API Access * **Root Cause:** The application is making a request to the Telegram Bot API using an invalid or revoked API token. The Telegram server is rejecting the request with a `401 Unauthorized` error. * **Simple Explanation:** The bot is trying to connect to Telegram's servers, but the "password" (API token) it's using is incorrect. Telegram doesn't recognize the bot, so it's refusing the connection. * **Potential Fixes:** 1. Verify that the Telegram Bot API token in your application's configuration (e.g., environment variables, config file) is correct and has no typos or extra characters. 2. The token may have been revoked. Use the `@BotFather` bot in Telegram to generate a new API token for your bot. 3. Update the application's configuration with the new token and restart it. * **Severity:** CRITICAL. The bot cannot receive messages or perform any of its core functions.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 5

2026-06-14T02:35:45.215673300Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates
Somchai Telegram Bot · Log

1 log error(s) detected

Error
Here is the error analysis for 'Somchai Telegram Bot'. ### Error: Telegram API Unauthorized * **Root Cause:** The application is trying to connect to the Telegram API using an authentication token that is invalid, expired, or has been revoked. The Telegram server is rejecting the connection attempt with a `401 Unauthorized` error. * **What Went Wrong:** The bot is trying to log into Telegram to check for new messages, but Telegram doesn't recognize its pa…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:31:11 UTC
View full analysis
Here is the error analysis for 'Somchai Telegram Bot'. ### Error: Telegram API Unauthorized * **Root Cause:** The application is trying to connect to the Telegram API using an authentication token that is invalid, expired, or has been revoked. The Telegram server is rejecting the connection attempt with a `401 Unauthorized` error. * **What Went Wrong:** The bot is trying to log into Telegram to check for new messages, but Telegram doesn't recognize its password (the API token). Because it can't log in, the bot cannot receive messages or respond to users. * **How to Fix:** 1. Check the application's configuration (e.g., environment variables, `.env` file) to ensure the Telegram API token is correct and hasn't been accidentally changed or corrupted. 2. If the token is correct, it has likely been revoked. Use the Telegram "BotFather" to generate a new API token. 3. Update the application's configuration with the new token and restart the service. * **Severity:** **CRITICAL**. The bot is completely non-functional and cannot process any user interactions.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 4

2026-06-14T02:30:40.624768663Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates
Somchai Telegram Bot · Log

1 log error(s) detected

Error
### Error: Unauthorized Access to Telegram API * **Root Cause:** The application is failing to authenticate with the Telegram API, receiving a `401 Unauthorized` error. This indicates the API token used by the bot is invalid, expired, or has been revoked. * **Simple Explanation:** The bot is trying to connect to Telegram to check for messages, but Telegram is rejecting its credentials. It's like trying to use a wrong or old password to log in to a service…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:26:03 UTC
View full analysis
### Error: Unauthorized Access to Telegram API * **Root Cause:** The application is failing to authenticate with the Telegram API, receiving a `401 Unauthorized` error. This indicates the API token used by the bot is invalid, expired, or has been revoked. * **Simple Explanation:** The bot is trying to connect to Telegram to check for messages, but Telegram is rejecting its credentials. It's like trying to use a wrong or old password to log in to a service. * **Suggested Fixes:** 1. Verify the Telegram bot API token stored in the application's configuration is correct and hasn't been accidentally changed or deleted. 2. If the token is correct, it may have been revoked. Generate a new API token using the "BotFather" on Telegram and update the application's configuration. 3. Check for any recent changes to the bot's settings on the Telegram platform. * **Severity:** **CRITICAL**. The bot is completely unable to receive messages or interact with users, rendering it non-functional.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 4

2026-06-14T02:25:35.754425657Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates
Somchai Telegram Bot · Log

1 log error(s) detected

Error
### Error 1: Unauthorized API Access * **Root Cause:** The application is making a request to the Telegram Bot API using an invalid API token, resulting in an `HTTP 401 Unauthorized` error. * **Explanation:** The bot is trying to communicate with Telegram's servers, but it's providing the wrong "password" (the API token). Telegram is rejecting the request because it doesn't recognize the bot. * **Suggested Fix:** 1. Verify that the API token (`...AAG8RoQW…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:20:54 UTC
View full analysis
### Error 1: Unauthorized API Access * **Root Cause:** The application is making a request to the Telegram Bot API using an invalid API token, resulting in an `HTTP 401 Unauthorized` error. * **Explanation:** The bot is trying to communicate with Telegram's servers, but it's providing the wrong "password" (the API token). Telegram is rejecting the request because it doesn't recognize the bot. * **Suggested Fix:** 1. Verify that the API token (`...AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw`) stored in your application's configuration (e.g., environment variables, secrets) is correct. 2. If the token is correct, it may have been revoked. Use the "BotFather" on Telegram to generate a new API token and update your application's configuration. * **Severity:** **CRITICAL**. The bot is unable to connect to Telegram to send or receive messages, rendering it completely non-functional.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 2

2026-06-14T02:20:33.912761860Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates
Somchai Telegram Bot · Log

1 log error(s) detected

Error
### Error: Telegram API Unauthorized * **Root Cause:** The API token used to authenticate with the Telegram service is invalid, expired, or has been revoked. The Telegram server is rejecting the bot's connection attempt with a `401 Unauthorized` error. * **What Went Wrong:** The application tried to connect to Telegram to check for new messages, but Telegram said the "password" (the API token) was incorrect. Because of this, the bot cannot communicate wit…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:15:42 UTC
View full analysis
### Error: Telegram API Unauthorized * **Root Cause:** The API token used to authenticate with the Telegram service is invalid, expired, or has been revoked. The Telegram server is rejecting the bot's connection attempt with a `401 Unauthorized` error. * **What Went Wrong:** The application tried to connect to Telegram to check for new messages, but Telegram said the "password" (the API token) was incorrect. Because of this, the bot cannot communicate with Telegram at all. * **To Investigate:** * Confirm that the API token in the application's configuration (e.g., an environment variable `TELEGRAM_BOT_TOKEN`) is correct and has no typos. * The token may have been revoked. Use the "BotFather" on Telegram to check the token's status or generate a new one. * Update the application's configuration with the new, valid token and restart it. * **Severity:** CRITICAL. The bot is completely non-functional and cannot receive or send messages.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 1

2026-06-14T02:15:29.372919455Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates
Somchai Telegram Bot · Log

1 log error(s) detected

Error
* **Error: Unauthorized by Telegram API** * **Root Cause:** The application is using an invalid, expired, or revoked API token to communicate with the Telegram service. The `401 Unauthorized` error is a direct rejection from Telegram's servers. * **What Went Wrong (Simplified):** The bot is trying to connect to Telegram to check for messages, but it's using the wrong "password" (the API token). Telegram doesn't recognize it and is blocking the connection.…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:11:33 UTC
View full analysis
* **Error: Unauthorized by Telegram API** * **Root Cause:** The application is using an invalid, expired, or revoked API token to communicate with the Telegram service. The `401 Unauthorized` error is a direct rejection from Telegram's servers. * **What Went Wrong (Simplified):** The bot is trying to connect to Telegram to check for messages, but it's using the wrong "password" (the API token). Telegram doesn't recognize it and is blocking the connection. * **Potential Fixes:** * Verify the Telegram Bot API token in your application's configuration (e.g., environment variables, secrets) is correct. * The token may have been revoked. Use the `@BotFather` bot in Telegram to generate a new API token and update your application's configuration with it. * Ensure the application is restarted after updating the token to apply the change. * **Severity:** CRITICAL. The bot is completely non-functional as it cannot receive any messages from users.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 11

2026-06-14T02:10:24.865230647Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates
Somchai Telegram Bot · Log

1 log error(s) detected

Error
### **Error: Telegram API Unauthorized** * **Root Cause:** The application is attempting to communicate with the Telegram Bot API using an invalid or revoked API token. The Telegram API server is responding with a `401 Unauthorized` error, rejecting the connection. * **What Went Wrong (in simple terms):** The bot is trying to log in to Telegram to receive messages, but the "password" (API token) it's using is incorrect. Telegram doesn't recognize the bot…
Status: Recorded Occurrences: 1 Last seen: 2026-06-14 02:06:24 UTC
View full analysis
### **Error: Telegram API Unauthorized** * **Root Cause:** The application is attempting to communicate with the Telegram Bot API using an invalid or revoked API token. The Telegram API server is responding with a `401 Unauthorized` error, rejecting the connection. * **What Went Wrong (in simple terms):** The bot is trying to log in to Telegram to receive messages, but the "password" (API token) it's using is incorrect. Telegram doesn't recognize the bot and is refusing to talk to it. * **How to Fix:** * Check the Telegram API token configured in the application. It may have a typo or have been revoked. * Use Telegram's "BotFather" to verify the current token for your bot. * If the token has been revoked, generate a new one with BotFather and update the application's configuration (e.g., environment variables, config files). * Restart the application after updating the token. * **Severity:** **CRITICAL**. The bot's core functionality (receiving messages) is completely broken, rendering the application useless.
View raw incident details 
Fingerprint: 6b435ea125d3
Occurrences: 10

2026-06-14T02:05:20.257785887Z bot loop error: 401 Client Error: Unauthorized for url: https://api.telegram.org/bot8909163788:AAG8RoQWY-8rmsuSvv4WfRsTFZv0VvgDqLw/getUpdates