Yes, I think I understood. When the service starts, a bot is created for each token in the database, then we trigger polling of the conversations. I’ll add a check that the username/password are properly configured and make an initial request to verify that everything works (instance is up + authentication), which, if it fails, cancels the creation of the bot and thus avoids infinite polling.
Sorry for the latency… I’m not very familiar with GitHub ![]()
But it’s done.
1 Like
I agree that it doesn’t bother at all… it was more to bring the info to your attention
1 Like