System Log Entry trigger - loop

[happymacrodroidcustomer]

Just sharing a funny experience as a warning...

Used System Log Entry trigger for first time today.

The macro was repeatedly invoked.

Uh duh...

Macro had Allow Logging checked. So
pattern match for System Log Entry trigger matched with macro execution entry in system log.

Moral of the story...
Possible workarounds include :
1) Set the trigger match text such that it will not match with the entry for the macro that has the trigger defined or
2) Uncheck Allow Logging or
3) Add a constraint on the trigger

 

[mapriex]

thank you for your input, i am trying around with the syntaxes, strangely its different than variable comparison syntaxes. do you know if there is a declaration list, where i can dig it?

in the description: it stands * and ? are wildcards, but i can't use it correctly.

also i can't find triggers for local system log entry, only for the global system log.

back to the topic, my test setup:
trigger: system log entry with one word

action: pop up - "it works"

after that i see how often and when it occurs or not. maybe similar to this can be used to prevent infinity loops.

if you want to run the test setup in the background, then you can use an inverting bool variable and check the local log data.

 

[Endercraft]

The system log entry trigger shouldn't be allowed to trigger on its own macro.. It might be something else.

 

[MacroDroidDev]

The system log entry trigger shouldn't be allowed to trigger on its own macro.. It might be something else.

This is certainly true and I have tried to prevent it. The interactions can be complex though so it's always possible there are edge cases where it can fail, so if anyone has an example of this submit the macro as a bug report and I'll try and fix it.