Since the external integrations were launched, I no longer receive my welcome (or update) message after a Gladys restart.
I think the message is sent before the Telegram integration starts, which can therefore not forward it to me…
The conversation:
The Telegram:
The scene:
Thanks for the feedback and screenshots, they helped identify the issue 
Your analysis is correct. Since Telegram is an external integration, Gladys sends pending messages as soon as the Telegram container connects. However, at that moment, the Telegram bot for the integration hasn’t started yet. Messages sent exactly at startup (your scene « Gladys starts », but also the message « Gladys has been updated ») are therefore rejected. They remain visible in the Gladys conversation, but they don’t arrive on Telegram. Incidentally, during the 5.3.0 update, only the release note link, sent a moment later, reached you.
A fix is proposed here: Deliver the messages Gladys sends while the bot is starting by cicoub13 · Pull Request #6 · GladysAssistant/gladys-telegram · GitHub. The integration will wait for the bot to be ready before sending. It will arrive with the next version of the Telegram integration, to be updated from the Integrations page.
In the meantime, you can add a « Wait » action of a few seconds (10 s for example) before your « Send a message » in the scene.
Well, sorry but no improvement.
Following this morning’s update, I realized the issue was still present:
Edit: I realize it hasn’t been merged… Sorry!
Hello, yes sorry I didn’t follow the topic (I couldn’t decide between the SDK and the integration)
I’ll get back to it next week
Oh no, no problem and no pressure! I just thought it was deployed, otherwise I wouldn’t have said anything 