DynamicGroupController and attributes

[3rdStng]

Running MSR "latest-26174-bd90c17c" via a docker within unRAID. With this latest docker update a day or two ago, Telegram stopped working. In looking at the logs, the ultimate error is that the chat_id is missing. I verified that my chat ID is still noted within the notifications YAML, but the reactor log still shows it failing. If I manually paste the chat ID into the notification field in the GUI, MSR will send the telegram message. It appears to be ignoring the "If left blank, the profile's default_chat_id value will be used."

Error log

[latest-26174]2026-06-26T18:04:45.814Z <Engine:INFO> Enqueueing "rule-2ajie2fd<SET>" (rule-2ajie2fd:S)
[latest-26174]2026-06-26T18:04:45.815Z <Engine:NOTICE> Starting reaction rule-2ajie2fd<SET> (rule-2ajie2fd:S)
[latest-26174]2026-06-26T18:04:45.815Z <Engine:INFO> rule-2ajie2fd<SET> all actions completed.
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:ERR> NotifyTelegram failure response from endpoint: 400 Bad Request
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:INFO> NotifyTelegram request URL: https://api.telegram.org/bot[[REDACTED]]:[[REDACTED]]/sendMessage
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:INFO> NotifyTelegram request body: {"text":"Test message","chat_id":""}
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:INFO> NotifyTelegram request headers: { "content-type": "application/json", "content-length": (undefined) }
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:ERR> NotifyTelegram request to https://api.telegram.org/bot[[REDACTED]]:[[REDACTED]]/sendMessage message Test message
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:CRIT> Error: NotifyTelegram request failed [-]
Error: NotifyTelegram request failed
    at NotifyTelegram.notify (/opt/reactor/server/lib/NotifyTelegram.js:300:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async NotifyTelegram.sendNotification (/opt/reactor/server/lib/Notifier.js:189:137)
[latest-26174]2026-06-26T18:04:45.983Z <Engine:ERR> Engine#1 reaction rule-2ajie2fd:S step 1 notification (Telegram) failed: [Error] NotifyTelegram request failed [-]
[latest-26174]2026-06-26T18:04:45.983Z <Engine:CRIT> Error: NotifyTelegram request failed [-]
Error: NotifyTelegram request failed
    at NotifyTelegram.notify (/opt/reactor/server/lib/NotifyTelegram.js:300:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async NotifyTelegram.sendNotification (/opt/reactor/server/lib/Notifier.js:189:137)
[latest-26174]2026-06-26T18:04:45.983Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat_id is empty"}

Snippet of the notification yaml with all the description text removed:

  # Telegram
  Telegram:
    profiles:
      default:
        description: Default Profile
        api_url: https://api.telegram.org
        bot_token: "[[REDACTED]]:[[REDACTED]]"
        default_chat_id: "[[REDACTED]]"

[wmarcolin]

If it might help with the investigation, here is the error message I'm getting when I run the query.

systemctl status reactor
● reactor.service - Multi System Reactor
Loaded: loaded (/etc/systemd/system/reactor.service; enabled; preset: enabled)
Drop-In: /etc/systemd/system/reactor.service.d
└─override.conf
Active: active (running) since Fri 2026-06-26 14:48:22 EST; 38min ago
Main PID: 6370 (MainThread)
Tasks: 11 (limit: 4599)
Memory: 112.8M (peak: 157.1M)
CPU: 28.239s
CGroup: /system.slice/reactor.service
└─6370 /usr/bin/node app -p

Jun 26 15:06:23 reactor node[6370]: at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:189:137)
Jun 26 15:06:23 reactor node[6370]: [latest-26174]2026-06-26T20:06:23.394Z Engine:CRIT Error: NotifyTelegram request failed [-]
Jun 26 15:06:23 reactor node[6370]: Error: NotifyTelegram request failed
Jun 26 15:06:23 reactor node[6370]: at NotifyTelegram.notify (/home/wilson/reactor/server/lib/NotifyTelegram.js:300:23)
Jun 26 15:06:23 reactor node[6370]: at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
Jun 26 15:06:23 reactor node[6370]: at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:189:137)
Jun 26 15:11:10 reactor node[6370]: [latest-26174]2026-06-26T20:11:10.209Z Engine:CRIT Error: terminated [preempted by rule state change]
Jun 26 15:11:10 reactor node[6370]: Error: terminated
Jun 26 15:11:10 reactor node[6370]: at Engine._process_reaction_queue (/home/wilson/reactor/server/lib/Engine.js:2091:47)
Jun 26 15:11:10 reactor node[6370]: at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
root@reactor:/home/wilson/reactor/logs#

[toggledbits]

OK. Fix coming soon...

[3rdStng]

I upgraded the docker to version latest-26177-be756a68. Unfortunately I am still not getting my Telegram alerts unless I put the Chat ID in the GUI. I don't know if it matters, but my chat_id starts with a "-". I think I have another chat ID that does not start/show as a negative ID. I can't test with that ID though.

[3rdStng]

Thank you @toggledbits. The latest-26177-3f86f4af build resolved the issue.

[wmarcolin]

I think my situation with Telegram is a little different. Version 26177 has actually partially resolved the sending issue.

I have two profiles set up, with two token and two ChatID, as you can see below (change the token and ChatID). For the first profile, I can send a message without entering the Chat ID in “Set Reaction.” For the second profile, if I leave it blank, it doesn’t send the message—it doesn’t use the settings I’ve configured. If I enter the Chat ID for the second profile, then the message sends perfectly.

  # Telegram
  Telegram:
    profiles:
      default:
        # description - A friendly description of this profile (for menus)
        description: Default Familia
        #
        # api_url - NOTIFICATION Access URL for Telegram API. Default is https://api.telegram.org/
        api_url: https://api.telegram.org
        #
        # bot_token - (required) Bot Token, from Telegram. See: https://core.telegram.org/bots
        bot_token: "xxxxxxxxxx:AAEOr9ZY4LxxxxxxxKPYJBSBxxxxxxxxxx"
        #
        # default_chat_id - (required) Default chat ID to use if not specified in message. See
        #                   this link for how to get chat ID:
        #                   https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id
        default_chat_id: "-1234567890"
        #
        # default_disable_notification - Default notification flag, may be either "true"
        #                                or "false". The system default is "false"
        #                                (false == notification enabled/not disabled).
        default_disable_notification: "false"
        #
        # default_parse_mode - Default message format/parse mode. The system default is
        #                      blank, for plain text. Other options: MarkdownV2, HTML
        #                      See: https://core.telegram.org/bots/api#formatting-options
        default_parse_mode: "HTML"
      wilson:
        # description - INFORMATION A friendly description of this profile (for menus)
        description: Default Wilson
        #
        # api_url - Access URL for Telegram API. Default is https://api.telegram.org/
        api_url: https://api.telegram.org
        #
        # bot_token - (required) Bot Token, from Telegram. See: https://core.telegram.org/bots
        bot_token: "xxxxxxxxxx:AAEFPoERxxxxxxxxkKFdEHc3txxxxxxxxxx"
        #
        # default_chat_id - (required) Default chat ID to use if not specified in message. See
        #                   this link for how to get chat ID:
        #                   https://stackoverflow.com/questions/32423837/telegram-bot-how-to-get-a-group-chat-id
        # 6272 default_chat_id: "1544809334"
        default_chat_id: "-1234567890"
        #
        # default_disable_notification - Default notification flag, may be either "true"
        #                                or "false". The system default is "false"
        #                                (false == notification enabled/not disabled).
        default_disable_notification: "false"
        #
        # default_parse_mode - Default message format/parse mode. The system default is
        #                      blank, for plain text. Other options: MarkdownV2, HTML
        #                      See: https://core.telegram.org/bots/api#formatting-options
        default_parse_mode: "HTML"

[wmarcolin]

@toggledbits I ran tests after upgrading Node.js, and the scenario is as described above; for the second profile, it only works if you enter the Chat ID.

[wmarcolin]

Now that the log file has fewer errors (Node.js), I can see this log message appear—I'm not sure if it helps.

[latest-26177]2026-06-28T23:20:20.829Z <NotifyTelegram:CRIT> Error: NotifyTelegram request failed [-]
Error: NotifyTelegram request failed
    at NotifyTelegram.notify (/home/wilson/reactor/server/lib/NotifyTelegram.js:304:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:188:145)
[latest-26177]2026-06-28T23:20:20.830Z <Engine:ERR> Engine#1 reaction rule-mevuuj8w:S step 3 notification (Telegram) failed: [Error] NotifyTelegram request failed [-]
[latest-26177]2026-06-28T23:20:20.830Z <Engine:CRIT> Error: NotifyTelegram request failed [-]
Error: NotifyTelegram request failed
    at NotifyTelegram.notify (/home/wilson/reactor/server/lib/NotifyTelegram.js:304:23)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async NotifyTelegram.sendNotification (/home/wilson/reactor/server/lib/Notifier.js:188:145)
[latest-26177]2026-06-28T23:20:20.831Z <NotifyTelegram:ERR> NotifyTelegram failure response text: {"ok":false,"error_code":400,"description":"Bad Request: chat not found"}

[CatmanV2]

I came here as I was seeing the same Telegram behaviour. I only have one profile. so am happy that the fix will resolve it for me

C

[toggledbits]

@CatmanV2 A subsequent (to the prior post) respin of build 26177 fixed multiple profiles as well, so you're good either way.

[CatmanV2]

As ever, my thanks. Upgraded to 26177 and all is well!

C