Anoying Messages "invoke because constraint failed:"...

[Lupus52]

Hello,

I have some macros working since some years. 100% perfect.

But since some month I have thousands of "errors" in the logs.

For example:

19-06-21 13:06:06 - Invoking Macro: WLAN Gisela
19-06-21 13:06:06 - Mit dem Netzwerk verbinden (MaxGast)
19-06-21 12:59:56 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:59:56 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:50:55 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:50:55 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:41:55 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:41:55 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:32:54 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:32:54 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:23:47 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:23:47 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:23:43 - Hintergrund wählen

The situation is absolute ok! The action should only trigger when Modus != condition. But NO messages if condition fails.

These messages are new for me! I think they came with one of the last updates.
How can I stop this "nonsense" of thousands messages of this type when a condition is false.

What does my macro? It recognizes the condition of a geofence "Gisela". If this is the first time when reaching the geofence and the Modus is != "Gisela" then it switches WLAN on, logs to the WLAN and so on. Then it sets the marker Modus = "Gisela".

If my phone looses the GPS-area "Gisela" (if inhouse) and finds it again, then there may not be a new trigger of the special loginmacro. ONly if the condition is false

Now I have a lot of these useless messages I don't had earlyer!

The same happens with a lot of other macros I use.

For example: A: Text ansagen (BT timeout) did not invoke because constraint failed: MacroDroid Variable (BT-off)

The macro should speak a text only when the variable "BT" is on.
And no message in the log when it is off.

or: A: Text ansagen (Auto off]) did not invoke because constraint failed: MacroDroid Variable (Auto off)

I have more than 40 macros. And my log is full of such "constraints"

Only "True" should be logged if I want. Not all "Falses" when constraints fail.

 

[Josué García]

Hello,

I have some macros working since some years. 100% perfect.

But since some month I have thousands of "errors" in the logs.

For example:

19-06-21 13:06:06 - Invoking Macro: WLAN Gisela
19-06-21 13:06:06 - Mit dem Netzwerk verbinden (MaxGast)
19-06-21 12:59:56 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:59:56 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:50:55 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:50:55 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:41:55 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:41:55 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:32:54 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:32:54 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:23:47 - GPS Gisela did not invoke because constraint failed: Modus != Gisela (GPS Gisela)
19-06-21 12:23:47 - GPS Gisela x did not invoke because constraint failed: Modus != Gisela (GPS Gisela x)
19-06-21 12:23:43 - Hintergrund wählen

The situation is absolute ok! The action should only trigger when Modus != condition. But NO messages if condition fails.

These messages are new for me! I think they came with one of the last updates.
How can I stop this "nonsense" of thousands messages of this type when a condition is false.

What does my macro? It recognizes the condition of a geofence "Gisela". If this is the first time when reaching the geofence and the Modus is != "Gisela" then it switches WLAN on, logs to the WLAN and so on. Then it sets the marker Modus = "Gisela".

If my phone looses the GPS-area "Gisela" (if inhouse) and finds it again, then there may not be a new trigger of the special loginmacro. ONly if the condition is false

Now I have a lot of these useless messages I don't had earlyer!

The same happens with a lot of other macros I use.

For example: A: Text ansagen (BT timeout) did not invoke because constraint failed: MacroDroid Variable (BT-off)

The macro should speak a text only when the variable "BT" is on.
And no message in the log when it is off.

or: A: Text ansagen (Auto off]) did not invoke because constraint failed: MacroDroid Variable (Auto off)

I have more than 40 macros. And my log is full of such "constraints"

Only "True" should be logged if I want. Not all "Falses" when constraints fail.

for some users this is of great help in the elaboration of large macros or to find errors or to know precisely what prevented the invocation of a macro, you can disable the logging of restrictions in System log > filter > uncheck the "Constraints" checkbox and you should no longer see those warnings (of any macro).

 

[Josué García]

Alternatively, if your macro works correctly and you don't need to see the specific log of that macro, you can choose to disable this macro from being logged, you can do it as shown in the attached file

Click on the button that in my case appears "26/28 macros enabled" and disable the macro that you do not want to be logged.

 

[Lupus52]

Hello,

thank you very much! I did not know this feature.