Tasker action limit

[Phil Bilton]

Hi pent,

From what I understand there is no limit on how many actions you can have in tasker but it seems to be any task I have that has over 300 actions in it can not be run by pressing the play button within the task.

I've looked in the logs and the task doesn't even start so it's not stopping due to error. When it's sorted as app they trigger fine out when triggering from a scene.

Cheers
Phil

[Sean Williams]

Hi Phil,

From what I understand there is no limit on how many actions you can have in tasker but it seems to be any task I have that has over 300 actions in it can not be run by pressing the play button within the task.

I've looked in the logs and the task doesn't even start so it's not stopping due to error. When it's sorted as app they trigger fine out when triggering from a scene.

From my experience although likely being highly frowned upon, 300 actions hasn't been a problem.

The only limitation I have found was if a task has 625+ actions it wont run when triggered by a profile.

[Phil Bilton]

Hi Sean,

I know it's frowned upon but it's necessary. I have 6 tasks that all gave between 300 and 500 actions. I get the football scores and split it all down and send it to a smart watch. All the data needs sorting in tasker as it's impossible to split it on the watch and display correctly.

On top of that, I need to account for errors, wether the games have gone into extra time, penalties etc. 

Not bring able to test when in the task isn't the end of the world because it still works but it's not convenient.

--
You received this message because you are subscribed to a topic in the Google Groups "Tasker" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/tasker/A-jCZZvclEM/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+unsubscribe@googlegroups.com.
Visit this group at https://groups.google.com/group/tasker.
For more options, visit https://groups.google.com/d/optout.

[Alexander Graetz]

Try to do this with a JavaScriptlet. It might run faster as well.

[Sean Williams]

I know it's frowned upon

Not by me :)

Not bring able to test when in the task isn't the end of the world because it still works but it's not convenient.

I'm at a loss as to your 300 action limit. Maybe it could be something to do with data size and not actions.

[Phil Bilton]

The task involves two for loops, a lot of if statements and even more sending variables through the watchmaker plugin. Some of the tasks are up to 700 or more actions.

[Richard Kemp]

It will absolutely run a hella load faster in JS.

OP, what you should do is break your task down into chunks. I.e. "task which grabs the data from the web", "task which takes the desired data from the page", "task which checks for correctness", etc. Then run all of these from one master task.

[Phil Bilton]

I wouldn't be able to do it JS, mainly because I have no idea on how to do it and the project has got so big I wouldn't know where to begin.

I know what should normally be done is break things down to smaller tasks but I've got so many local variables, would they carry over to the other tasks if actions from the main task?

The task itself runs fine and it's not too long in terms of time it takes really. The thing that slows it down is sending all the variables to watchmaker. For one of the tasks there is over 160 variables sent to watchmaker. I've got two of these tasks that are identical apart from they represent different football leagues so that's 320 variables across two tasks. 

I've now added league tables to the app and the two tasks for that come in at 360 variables across two tasks.

As I've mentioned somewhere before, I can't send the variables across in a batch because they can't be split and processed in watchmaker which is used to display it all, so all the variables need to be sent individually.

On 5 Sep 2017 09:26, "Richard Kemp" <richar...@gmail.com> wrote:

It will absolutely run a hella load faster in JS.

OP, what you should do is break your task down into chunks. I.e. "task which grabs the data from the web", "task which takes the desired data from the page", "task which checks for correctness", etc. Then run all of these from one master task.