Dear Latenode Support,
I am writing to you again regarding a critical issue with my Telegram bot scenario that I have been unable to resolve despite extensive troubleshooting. I believe there is a fundamental problem with how Latenode is handling message routing and filter conditions, and I require your urgent attention to this matter.
I have a single scenario designed to handle two distinct types of Telegram messages:
- “/start” commands: These should trigger a greeting response.
- Audio messages: These should be processed by my audio processing logic.
However, I am experiencing the following, consistently reproducible behavior:
- When I send the “/start” command, the scenario intended for handling audio messages is triggered instead.
- Conversely, when I send an audio message, the scenario for handling the “/start” command is triggered.
This is the case even when both the audio processing and the “/start” command logic are within the same scenario, using separate filter conditions.
My filter conditions are as follows:
- “/start” filter:
$1.data.update.message.text == "/start" - Audio filter:
$1.data.update.message.audio?.mime_type contains "audio/mpeg"
I have attempted the following troubleshooting steps, all without success:
- Restarting scenarios
- Clearing browser cache
- Using different browsers
- Simplifying scenarios to the bare minimum
- Explicitly checking for null values
- Using alternative filter expressions
The fact that the incorrect scenario is triggered for each message type indicates a serious flaw in Latenode’s core functionality. I have provided detailed information, including screenshots and examples, in previous communications.
I urge you to investigate this issue thoroughly and provide a solution as quickly as possible. My bot is currently non-functional, and this is impacting my ability to deliver a working solution.
Thank you for your prompt attention to this urgent matter.
Sincerely