1
Solved

(tasker 5.7.1 & 5.7.2) %err is not set by failing ping action

I cannot update to 5.7.1 or 5.7.2 because if I do,  an important task of mine no longer works.

I use the ping action (retries=2), configured to continue task after error occurs (e.g. if target hist is unreachable)

However in the case that the host is unreachable %err is not set. Therefore the following conditional execution which checks %err is wrong.

This used to work in earlier versions of tasker e.g 5.6.

Follow

2 replies

Votes Newest Oldest
S

Hi,

thanks for the quick reply.

This is the sequence of what I do:

1. "Variable Clear" on %err

2. "Action ping www.google.com" with 2 retries and continue on error.

3. set %ping_err to %err if %err is set

4. if %ping_err is set do something_A

    else do something_B

    endif

======

Using Tasker 5.6: immediately after the ping action (if target is unreachable), %err is defined and has the value 1.

======

Thanks. Have you tried using %errmsg?

Also, the %err variable will be available again on the next version. Thanks

Thanks for the report. What was %err set to before?

Also, try using the %errmsg variable instead.

Topic is closed for comments