Tasker for scheduled browser refresh unpredictable

[Nerdgirllondon88]

So I created a profile with a task to open a specific website on a regular basis.

The reason being is I want to stay logged into a website profile th a times out after 20 minutes.

I have added a 'write file' task which adds the day and time to a text file every time performs this task so I can check it is performing. Which seems to works well.

Problem is it appears sometimes it works sometimes it doesn't .. for example it works for a while then stops. Then I test it and it works fine for a while then stops again.

I used the profile "time" , and put it as repeating every 15 mins. All day. Then added the task.

 

[Thom]

Welcome to Android Forums.

How long is "a while"?
When setting the condition ... does it have only repeat specified with no start or end time?

... Thom

 

[Thom]

I have run this one for the last three hours and a half with no problem ...

Profile: _test
Time: Every 2m
Enter: Anon
A1: Flash [ Text:-- %TIME -- Long:On ]

... Thom

 

[electricpete]

If you are on marshmallow, go to android settings and exclude tasker from "battery optimisation" (doze)

 

[Nerdgirllondon88]

Thanks for your replies. Just to answer some of your questions. I'm on kitkat not marshmallow. The profile works for about 2 hours then stops.

Profile: Launch url repeat
Time: Every 15m
Enter: Lauch Url
A1: Launch App [ App:Chrome Data:http://www.(website).com/Android/

 

[Nerdgirllondon88]

I think it does have something to do with the phone dozing off, but there is no way to change power settings.

I have used macrodroid to schedule the phone to stay awake continuously, but doesn't seem to work indefinatey. Plus I thought with Android the system can force tasks to override sleep? That is partly why tasker works better than anything is ios because ios can't do that.

 

[electricpete]

Are you on marshmallow (Android 6.0+)? If yes, then it is in the system settings somewhere. For me (nexus 6 running 6.0.1), it is: apps /gear-icon / battery optimization

Also (regardless of android versions) there are a few settings within tasker itself that help prevent it from getting killed on low memory (mostly for older phones...although I had problems with tasker getting killed on my S4 running lollipop.... confirmed it in the event log "restart monitor service"). In tasker menu look at Preferences....select monitor tab...then look at outings for "run in foreground", "notification icon" and "reliable alarms" (press the ? for more info about these options)