Unreliable HTTP_REQUEST to Telegram API tasks
thisisnota_love_song
Environment
Phone: Samsung Galaxy
Android Version: 13 / SDK 33
One UI Version: 5.1
Tasker Version: 6.2.22 (installed via Google Play).
I purchased tasker a couple of years ago in Google Play, but couldn't get to grips with it. I've changed my phone in the last few days and, after a factory reset, installed tasker on it. I'm not sure how to tell whether my current installation is licensed, or activated, but I've not seen any screens saying it's a trial or anything. How can I confirm for sure?
I've created a bot on telegram and added it to a private group as an Administrator.
The bot reliably sends to the group all the messages I send to it using curl. I can invoke it in a bash loop and send 20+ messages without any delay between them. All messages arrive.
I have a very reliable internet connection.
I created two HTTP_REQUEST tasks; one for sending a message "Missed call", after a missed call, and one for sending a "New SMS" message when a new SMS has been received. To keep it simple for the moment, neither use variables.
I've created a profile for each, and linked each one to the respective task.
This works intermittently, but not reliably; sometimes it sends a message, and sometimes it doesn't. It doesn't matter if I wait between testing them, or test in rapid succession.
I've given all the permissions that Tasker has asked for, and checked tasker in "Apps settings", and the permissions seem correct.
I've ensured that the app can use the battery unrestricted. Anyway, while testing, the phone has been in "Always on display" mode, and Tasker has been open.
Strangely, Tasker seems to be the only app that does not appear in the apps that can be added to the "Never auto-sleeping apps", so I can't add it to that.
When I open a task ("Task Edit"), there are play and "fast forward" buttons at the bottom. tbh, I don't know what these are, as I can't find them in the user guide. If I keep pressing the fast-forward button, it seems to send test messages to the bot. When they are successfully sent, there's haptic feedback. If no message is sent, then no haptic feedback happens.
Sometimes after it fails to send a message, an error log is sometimes briefly shown, as follows. I don't know if this is the source of the problems, or a separate issue.
```
17.42.30/LicenseCheckerTasker Checking cached only
17.42.30/LicenseCheckerTasker cache validity left -668643
17.42.30/LicenseCheckerTasker Cached status: Licensed
17.42.30/LicenseCheckerTasker Cached only: Licensed
17.42.30/Ew add wait type EasyAction1 time 2147483647
17.42.30/Ew add wait type EasyAction1 done
17.42.30/E add wait task
17.43.00/E Error: 1
17.43.00/E java.util.concurrent.TimeoutException: The source did not signal an event for 30000 milliseconds and has been terminated.
```
Can anyone help me solve this, please?
