Avoid using "Wait" action?

[Daniel D]

Hello there!
I've been reading here ant there about the "Wait" action inside Tasker and how it blocks action flows. After all this I haven't manage to figure this out: is it a good practice to try to avoid using "Wait" all together? Maybe replace it with time triggered external profiles, where the trigger time is set in the current task (the one that needed "Wait" in the first place)?
What are your thoughts and practices regarding this subject?
Thanks!

[Rich D]

> I've been reading here ant there about the "Wait" action inside Tasker and how it blocks action flows.

Take note of the date of the posts you read on this subject. The older the post the less relevant it is likely to be. Pent (with a little help) has done a great job at addressing the historical wait bugs. The conventional thinking has always been to avoid long waits whenever possible and if you need a long wait then do a loop with many small waits to give other tasks a chance to run. I have tested long waits (under 12 hrs) on my device  and would guess I have average to above average number of profiles and tasks running daily. I have found no issue with using long waits. Once a wait is encountered in a task any task is then allowed to run even those with a lower priority. With the exception of a child  of a preform task action. A parent will not run until the child task of equal or higher priority has finished even if a wait is encountered.

My general practice now is I will use a time context or repeating time context instead of the long wait if possible. I will not use a variable time context to avoid a long wait. The variable time context is certainly usefull but just seems like it is  too complex just to replace a wait.

I have not seen any posts lately conserning waits. So my humble opinion would be not to shy away from them, and if you do encounter a issue then report it so it can be fixed. 

I should mention there is one outstanding bug conserning waits. In some cases when you use the return function for a preform task action if there is a wait action in the parent just after the return the wait will get stuck and does not seem to end. I am just going off memory for this one so the details could be off.  I will post a bug report on this one once I get my facts straight.

[SportyRydr]

Hey, Rich, thanks for the update and elaboration on Waits! I also read something a while back that caused me to try to avoid them. It's nice to know they're "safe" again. ;)

Take care.

[Rich Belthoff]

Rich,

I know this is a bit old, but what do you mean by repeating time contexts? My battery on my Nexus 6P doesn't last very long. I'm pretty sure it's related to mobile data. So, if I'm not connected to WiFi, I want to cut it off a while, turn it back on for a minute or so, and then cut it off, doing this repeatedly throughout the day. I thought maybe your repeating time context might work? Thanks.

-Rich B

On Monday, October 17, 2016 at 6:35:55 PM UTC-4, Rich D wrote:

[Rich D]

I know this is a bit old, but what do you mean by repeating time contexts? My battery on my Nexus 6P doesn't last very long. I'm pretty sure it's related to mobile data. So, if I'm not connected to WiFi, I want to cut it off a while, turn it back on for a minute or so, and then cut it off, doing this repeatedly throughout the day. I thought maybe your repeating time context might work?

I meant a time context with the 'Repeat'  option checked.  It Should work for what you are looking to do.  You can  still set a a from and till time like 09:00am  till  5:00 pm then check the repeat option and enter how often you want the profile to go active. In the task, I would turn on  mobile data  then use a 1 minute wait  then turn off mobile data. 

[Rich Belthoff]

Ok got it. Thanks.