-
-
Notifications
You must be signed in to change notification settings - Fork 69k
Telegram multi-account bindings not routing to correct agent #803
Copy link
Copy link
Closed
Labels
bugSomething isn't workingSomething isn't working
Description
Problem
When configuring multiple Telegram bot accounts with bindings, messages from non-default bots are still routed to the default agent instead of the bound agent.
Config
"telegram": {
"enabled": true,
"accounts": {
"steve": {
"botToken": "...",
"dmPolicy": "pairing"
},
"opie": {
"botToken": "...",
"dmPolicy": "pairing"
}
}
},
"bindings": [
{
"agentId": "opie",
"match": { "provider": "telegram", "accountId": "opie" }
}
]Expected
Messages to the opie Telegram bot should route to agent:opie:... sessions.
Actual
All Telegram messages route to agent:main:... regardless of which bot received them.
Notes
- Both bots are valid and responding to getMe API calls
- Removing the top-level
botToken(keeping onlyaccounts) didn't fix it - MS Teams binding has the same issue ([Bug]: Messages/responses leak between providers (cross-provider routing) #788 related?)
- Gateway restarted after config changes
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working
Type
Fields
Give feedbackNo fields configured for issues without a type.