Tasker stops the task suddenly

[Ayman Sho]

Hi there,

I made a task that controls my A/C through RC app .

The task carries a series of actions starting by awaking my phone , loading the RC app , then automatically pressing the desired button (via RunShell script) then returning to tasker again and waiting for a specified period ,then repeating the previous steps with another RC button pressed ,etc . Looping these actions is done with a variable set to count at the beginning and a value added to the variable at the end , so that if a target value is reached ; the task stops ( eg. after 6 hrs of continuous A/C On & Off commands) .

The problem is that the incidence of success in performing this task accurately is nearly 50% 

ie. in 50% of trials , Tasker will stop the task before the specified time has passed (eg.stops after 2 hrs and not 6) , noticing that Always the stoppage is at the RC app (ie. fails to return to tasker interface and complete the rest of series ), so when I awake my device I find the RC App loaded & when I return to tasker I find the task has ended.

On the other 50 % , the same task willl run successfully for the whole 6 hrs of continuous commands without abrupt causeless stopping , making it difficult for me as a beginner to diagnose the problem.

Any help please....

Thanks.  

[Matt R]

Enable and check the run log (menu > more > run log).

Matt

[Brandon Horwath]

'Keep device awake' enabled in task properties?

[Ayman Sho]

No.. It's Not enabled

[Brandon Horwath]

... then 'enable' that option.

Does that resolve some reliability issues?

[Ayman Sho]

Enabled the Run log and it revealed a status of (ExitErr) at the time of task failure... What does that mean :( ?

[Ayman Sho]

Another thing which might be of significance is that the % of failure highly increases if I run a task after stopping a previous one ... so I always restart the device before running the new task , however it's Not totally effective .

[Rich D]

> Enabled the Run log and it revealed a status of (ExitErr) at the time of task failure... What does that mean :( ?

The run log has its own section in the user guide.

Tasks

RejBad
task was rejected because it was malformed task e.g. had no actions
RejCopy
task was rejected because it's a second copy of a task which has Abort New Task set for Collision Handling in its preferences
RejMaxQ
the maximum number of queued tasks (determined in Action preferences) has been reached
RejOff
Tasker was disabled at the time the task was submitted
Running
the task has been entered in the run queue. Other tasks may still have their actions executed before this one (see Task Scheduling)
ExitErr
the task has stopped after an error
ExitOK
the task has finished all its actions and stopped
ExitRep
the task has stopped because a second copy of it has arrived and Abort Existing Task s specified for its Collision Handling preferences
ExitKill
the task has been stopped because the execution service is stopping

Try enabling 'pop up errors' in the tasker preferences. These will only show when entering or re-entering the Tasker UI.

[Matt R]

Which action failed?

Matt

[Ayman Sho]

yeah , the action that seems to always fail is performing a short beep after pressing the button ( RunShell) .

 Frankly, these were the only 2 actions that I did not separate by a short period (eg. a second ) .... 

I 'll separate them and follow up ...

Seems promising :)      

On Friday, 27 June 2014 18:43:07 UTC+2, Matt R wrote:

Which action failed?

Matt

[Ayman Sho]

Enabled "Keep device awake".... didn't solve the problem :)

I'll separate the beep action from the runshell by a second of time and followup..  

[Ayman Sho]

Still failing at the beep action .... will disable it and observe ....

[Ayman Sho]

Hi Matt .... Sadly, the task still fails after the Runshell action ... Actually this is the only action that needs root permission .... The problem maybe related to Superuser while granting it the permission ..... Any Help please. :(  

[Ayman Sho]

I've enabled the option (continue after error) for all runshell actions of the task . If that worked ,it would nearly solve my problem , as i can accept a failure in 1 or 2 of the runshell actions But i can't accept stoppage of all the task on top of a runshell failure .   

[Rich D]

>
> I've enabled the option (continue after error) for all runshell actions of the task . If that worked ,it would nearly solve my problem , as i can accept a failure in 1 or 2 of the runshell actions But i can't accept stoppage of all the task on top of a runshell failure .   
>
>

Did you try enabling the pop up errors?

What is the error shown in the run log?  ExitErr?

Could you post the task description along with a which  action is failing

To post your profile or task here...  Long press on the profile or task name / ( 3 dot menu with 4.0+ ) export / export description to clipboard (not XML)

Any linked tasks will be exported with the profile they are linked to..

To be able to export, The beginner mode needs to be off and the profile needs to be named by you (Not the Tasker listed name.  Tasker will list your profile with the context name if you have not given it one).

[Ayman Sho]

haven't enabled popup errors yet ... how could it help ?

Yeah the error shown is ExitErr

The action that causes the whole task to fail is definitely the RunShell

 The task description seems to be too long , however I'll post it in the next post.

[Brandon Horwath]

That's the xml, the description might be shorter ;-)

[Ayman Sho]

Sorry... That's the task description

Sharp AC (59)
A1: Variable Set [ Name:%count To:0 Do Maths:Off Append:Off ]
A2: Secure Settings [ Configuration:Screen & Keyboard Lights On
5 Seconds Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
A3: Launch App [ App:Power IR - Universal Remote Pro Data: Exclude From Recent Apps:Off ]
A4: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ]
A5: Run Shell [ Command:input tap 570 120 Timeout (Seconds):0 Use Root:On Store Output In: Store Errors In: Store Result In: Continue Task After Error:On ]
A6: Beep [ Frequency:10055 Duration:318 Amplitude:10 Stream:3 ]
A7: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ]
A8: Run Shell [ Command:input tap 1220 220 Timeout (Seconds):1 Use Root:On Store Output In: Store Errors In: Store Result In: Continue Task After Error:On ]
A9: Beep [ Frequency:10055 Duration:318 Amplitude:10 Stream:3 ]
A10: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ]
A11: Button [ Button:Back Continue Task After Error:On ]
A12: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A13: Button [ Button:Back Continue Task After Error:On ]
A14: Wait [ MS:0 Seconds:0 Minutes:15 Hours:0 Days:0 ]
A15: Secure Settings [ Configuration:Screen & Keyboard Lights On
5 Seconds Package:com.intangibleobject.securesettings.plugin Name:Secure Settings Timeout (Seconds):0 ]
A16: Launch App [ App:Power IR - Universal Remote Pro Data: Exclude From Recent Apps:Off ]
A17: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ]
A18: Run Shell [ Command:input tap 700 120 Timeout (Seconds):0 Use Root:On Store Output In: Store Errors In: Store Result In: Continue Task After Error:On ]
A19: Beep [ Frequency:10055 Duration:318 Amplitude:10 Stream:3 ]
A20: Wait [ MS:0 Seconds:2 Minutes:0 Hours:0 Days:0 ]
A21: Button [ Button:Back Continue Task After Error:On ]
A22: Wait [ MS:0 Seconds:1 Minutes:0 Hours:0 Days:0 ]
A23: Button [ Button:Back Continue Task After Error:On ]
A24: Wait [ MS:0 Seconds:0 Minutes:15 Hours:0 Days:0 ]
A25: Variable Add [ Name:%count Value:1 Wrap Around:0 ]
A26: Goto [ Type:Action Number Number:2 Label: ] If [ %count < 32 ]

[Rich D]

> haven't enabled popup errors yet ... how could it help

The error description could give you a hint of how to fix the issue.

You could also use the 'store errors in' option in the run shell command. Just store them to a global variable then check the variables list after a failure .

>> > I've enabled the option (continue after error) for all runshell actions of the task .

Has that worked so far?

Does it always fail on the first run shell command ? Or exactly which action number does it always fail on?

[Ayman Sho]

There is No failure till now since "Continue after error" option is enabled .

But i still can't judge except after answering this question " How is the status of this option interpreted in the Run log ?" 

In other words , to get sure of the effectiveness of this option... I need the RunLog to reveal a runshell error after which the task continued ...

Otherwise it may be running fine Not due to the option but - as i mentioned before - the 50 % incidence of success. 

Still observing ... Hope that the problem is in its way to be solved . 

[Rich D]

> There is No failure till now since "Continue after error" option is enabled .
> But i still can't judge except after answering this question " How is the status of this option interpreted in the Run log ?" 
> In other words , to get sure of the effectiveness of this option... I need the RunLog to reveal a runshell error after which the task continued ...

The run log will not show this. However the error is easily obtained by my previously mention approach of storing the error in a global variable form the 'store errors in' option in the run shell action. 

> Otherwise it may be running fine Not due to the option but - as i mentioned before - the 50 % incidence of success. 
> Still observing ... Hope that the problem is in its way to be solved . 
>
>
> On Saturday, 28 June 2014 23:18:21 UTC+2, Rich D wrote:
>>
>>
>> > haven't enabled popup errors yet ... how could it help
>>
>> The error description could give you a hint of how to fix the issue.
>>
>> You could also use the 'store errors in' option in the run shell command. Just store them to a global variable then check the variables list after a failure .
>>
>> >> > I've enabled the option (continue after error) for all runshell actions of the task .
>>
>> Has that worked so far?
>>
>> Does it always fail on the first run shell command ? Or exactly which action number does it always fail on?
>

> --
> You received this message because you are subscribed to the Google Groups "Tasker" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to tasker+un...@googlegroups.com.
> Visit this group at http://groups.google.com/group/tasker.
> For more options, visit https://groups.google.com/d/optout.

[Ayman Sho]

Hi Guys...

I can say that after i enabled "Continue after error" ,there are No errors so far .

Satisfied with this result so far .

Hope I could know the cause of unexplained Runshell failure.

Thank you guys for all your help  .

On Thursday, 26 June 2014 21:35:09 UTC+2, Ayman Sho wrote:

[Rich D]

> Hope I could know the cause of unexplained Runshell failure.

I have explained how to get the error 2 different ways  3 separate times and so far you have not posted any results. That would be a good place to start if you are looking for the cause of the error.

[Ayman Sho]

I've done what you said 2 days ago....  But as I said... Now there are No failures in runlog and no errors in the defined global value...  I may try later to redisable "continue after error"  to get the previous errors. Thank you for your great help.

On 1 Jul 2014 03:14, "Rich D" <ricp...@gmail.com> wrote:

> Hope I could know the cause of unexplained Runshell failure.

I have explained how to get the error 2 different ways  3 separate times and so far you have not posted any results. That would be a good place to start if you are looking for the cause of the error.

--
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/SqZrUrtqhFY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to tasker+un...@googlegroups.com.