Message Formats¶
The Telegram bot offers four message formats โ pick one in notifications.telegram.messageFormat.
Banks-overview only. Default.
Transaction details with amounts.
Monospace table layout.
Phone-friendly variant¶
When listenForCommands: true, the logger format auto-switches to phone (no emojis, compact lines) so that /logs output is readable on a small screen. Message format stays whatever you chose.
On failure¶
๐จ Import Failed
๐ Authentication Error (discount): Invalid credentials. Please verify your password.
Errors are categorized so users can self-serve fixes: authentication, captcha, rate-limit, password change required, network. Each category includes a one-line action hint.
Partial runs¶
Every bank is imported in its own child process, so one bank failing never cancels the others. When a Telegram-triggered import finishes with a mix of outcomes, the bot reports exactly which banks failed instead of implying the whole run was lost:
โ ๏ธ Partial import (38s) โ 4/5 banks OK, 1 failed:
โข paybox: Invalid credentials. Please verify your password.
Use /retry to re-run the failed bank(s), or /logs for details.
Only when every bank failed does the message read as a total failure:
/status uses the same distinction and shows partial: 4/5 OK for a mixed run.
Each child process also sends its own ๐จ Import Failed message when none of the banks it was given succeeded. That message names the bank and the reason rather than reporting a bare status token, so a single-bank child never reads as a total outage:
When a child was given several banks and every one of them failed, the message states the count and lists up to five banks, eliding the rest:
๐จ Import Failed
All 3 banks failed โ visacal: zero accounts; max: login rejected; leumi: timeout
See also¶
- Telegram setup
- Webhook payloads
- Logging โ controls log file output, separate from Telegram message format