BUG: Telegram Monitoring Failure - Test message works, but Hourly Heartbeat is NEVER sent

[demolayy]

Environment:

OS: Debian 12 (Bookworm)

Status: Bot Token and Chat ID VALIDATED (Test message received successfully).

The Problem:
While the initial "Test Message" during setup or manual trigger works perfectly, the hourly monitoring/heartbeat messages (scheduled for every full hour, e.g., 14:00, 15:00) are never dispatched.

Technical Details:

Manual Test: SUCCESS (The bot is connected and the Chat ID is correct).

Automated Heartbeat: FAILED (The user waited for the 14:00 check-in and received nothing).

Expected Behavior: A status summary including uptime, bandwidth, or relay health every hour.

Actual Behavior: Total silence from the bot after the initial test message.

Observations:
The script responsible for the hourly loop or the cron job inside the container is likely failing to trigger the notification function. Since the network path to Telegram's API is proven to be open (due to the successful test), this is a logic error in the Torware scheduling code.

Requested Fix:

Check the crontab or the while true loop responsible for the hourly status.

Ensure the monitoring script has the correct environment variables (Token/ID) exported for the automated tasks, not just for the interactive setup.

Add a log entry to torware logs whenever a Telegram notification is attempted (Success or Failure).