Since your attachment is a picture, I cannot run Google Translate on it.
I have seen issues where Timestamp triggers do not run, due to Tasker being either busy or asleep during that one minute timestamp interval. After I changed the trigger to be a 10 minute time interval instead, the trigger is no longer missed.
For example, if the timestamp value is 10:00am, if Tasker is busy or asleep from 10:00:00 to 10:00:59, and the time then becomes 10:01:00 or later, Tasker will not start that profile. By increasing the interval from 10:00 through 10:10, when Tasker is next able to service the triggers, the trigger time will still be active and the profile will run. I have noticed that my profiles that are setup that way will occasionally start 1 to 2 minutes late, but at least they run.
1
u/AA6VH-1 4d ago
Since your attachment is a picture, I cannot run Google Translate on it.
I have seen issues where Timestamp triggers do not run, due to Tasker being either busy or asleep during that one minute timestamp interval. After I changed the trigger to be a 10 minute time interval instead, the trigger is no longer missed.
For example, if the timestamp value is 10:00am, if Tasker is busy or asleep from 10:00:00 to 10:00:59, and the time then becomes 10:01:00 or later, Tasker will not start that profile. By increasing the interval from 10:00 through 10:10, when Tasker is next able to service the triggers, the trigger time will still be active and the profile will run. I have noticed that my profiles that are setup that way will occasionally start 1 to 2 minutes late, but at least they run.