This topic was automatically generated from Slack. You can find the original thread here.
setting telegram bot trigger results in this error “Failed to fetch dynamically imported module: https://pipedream.com/_static/deployComponent.9deefee2.js”
This topic was automatically generated from Slack. You can find the original thread here.
setting telegram bot trigger results in this error “Failed to fetch dynamically imported module: https://pipedream.com/_static/deployComponent.9deefee2.js”
I’m sorry to hear you’re experiencing an issue with the Telegram bot trigger. To better assist you, could you please provide more information about your workflow setup and any additional steps you’ve taken? This will help me understand the context and provide a more accurate solution.
i am setting a telegram trigger with new bot command
To set up a Telegram trigger with a new bot command, follow these steps: 1. Register the new command with the BotFather in Telegram. Send a message in this format for each command you’d like to register: command - description
For example: ```
hi - send greeting bye - send bye now
i kept getting this error message “Failed to fetch dynamically imported module: https://pipedream.com/_static/deployComponent.9deefee2.js”
I apologize for the inconvenience you’re experiencing. It seems like there might be an issue with the Pipedream platform or a temporary glitch. Please try the following steps: 1. Refresh your browser and try setting up the Telegram trigger again. 2. Clear your browser cache and cookies, then try again. 3. Try using a different browser or an incognito/private browsing window. If the issue persists, I recommend reaching out to Pipedream support at https://pipedream.com/support for further assistance.
that definitely sounds like a bug. Can you please include a screenshot and file a bug report here? The team will take a look.
I’ll post screenshots here if i ran into it again
Seems working for now, so pipedream could only add one listening for telegram bot source, is that right?
That’s right, that’s a restriction on Telegram’s end. You can only register 1 webhook at a time.
But we should return that information explicitly when you run into that issue, instead of the error you described.
i’ll let you know if i run into it