I've used the attached macro to test MD wait for trigger behaviour when the macro is disabled. The wait for trigger has a continue timeout set for 10 seconds.When the macro is disabled, it's not able to detect the trigger but will still timeout.
This happens with any trigger, not just the one used in the example recording.
Version: 5.37.12
Shouldn't the timeout continue to keep going like with the Wait until next action action? If it changes your timeout to no timeout I wouldn't say it's working as expected.It appears that when the macro is disabled on a wait for trigger with timeout, the timeout is stopped. Re-enabling the macro doesn't appear to restart the timeout, which makes sense.
If it was already disabled before being run it should say in the log based on my initial testing. Perhaps you thought it didn't complete since the popup didn't show due to it being disabled.Unfortunately, I'm not seeing the timeout complete when the macro is disabled.
Is this on the beta? I have not seen a single warning after repeating your tests.When I disabled the macro MD generated a warning message - see the attached system log. I didn't get a warning message when the timeout was set to continue.
I believe disabling a macro stops all processing of the macro actions including any ongoing timeout.Shouldn't the timeout continue to keep going like with the Wait until next action action? If it changes your timeout to no timeout I wouldn't say it's working as expected
I thought it only seemed like it did due to how fast it goes through the actions (hence the importance of the Wait for next action action).I believe disabling a macro stops all processing of the macro actions including any ongoing timeout.
Re<enabling the macro and it never ran the action after the wait action. The popup message never displayed and the system log did not show any actions.
I believe this is the expected behaviour.
Isn't this supposed to be where I report bugs?If you are convinced it is not working as it should, I suggest you generate a bug report.
No...report bugs from MD.I thought it only seemed like it did due to how fast it goes through the actions (hence the importance of the Wait for next action action).
Isn't this supposed to be where I report bugs?
Thanks. Was looking at the beta feedback thread and thought this was what the dev meant by "troubleshooting section".No...report bugs from MD.
Select the 3 dots ....top left hand corner
Select Toubleshooting
Select Report a Bug
Not sure what your test macro has to do with the issue, as there is no wait for trigger action.
To show that disabling doesn't stop the macro but rather skip or prevent the actions from actually doing anything.I believe disabling a macro stops all processing of the macro actions including any ongoing timeout.
The system log shows actions from test macro such as wait for trigger which aren't in the screenshot of macro test.Thanks. Was looking at the beta feedback thread and thought this was what the dev meant by "troubleshooting section".
To show that disabling doesn't stop the macro but rather skip or prevent the actions from actually doing anything.
Those are from previous tests before I reconfigured. Check out the latest test. But anyway, I reuploaded it with the log cleared.The system log shows actions from test macro such as wait for trigger which aren't in the screenshot of macro test.
So I still don't see how you claim disabling a macro doesn't stop but rather skip or prevent actions from doing anything, not from your screenshots.
The uploaded macro hasn't changed.Those are from previous tests before I reconfigured. Check out the latest test. But anyway, I reuploaded it with the log cleared.
What do you mean? The log matches the contents of the macro now, what else is there to change?The uploaded macro hasn't changed.
Yeah, I just did. The issue I originally reported with it not responding while disabled and the one you found about the timeout not resuming after reenabling.Have you submitted a bug report?
The test macro is for a wait action not a wait for trigger. So this doesn't show the original issue.What do you mean? The log matches the contents of the macro now, what else is there to change?
Yeah, I just did. The issue I originally reported with it not responding while disabled and the one you found about the timeout not resuming after reenabling.
The screenshots in the reply were in response to this:The test macro is for a wait action not a wait for trigger. So this doesn't show the original issue.
You made it sound like it stops the processing of any module, so I used a Wait until next action action to show that it continued to work even after the macro was disabled.I believe disabling a macro stops all processing of the macro actions including any ongoing timeout.
So no, they weren't for the bug I originally reported. There's another set of screenshots in the OP for that.Is this the macro you used to report the bug?
Same result if I wait for longer than a second before reenabling. Interestingly enough, it seems that it remains that way as long as it's 4 seconds or less; any longer than that and it'll get cancelled as soon as it's disabled.It is not displayed whenever I disable the test macro, even if I subsequently enable it.
But if your assertion is correct shouldn't it be displayed?
Why the difference in test results?
Perhaps the difference is that in your test you are only giving MD 1 sec to disable a macro before enabling the macro. That may be too fast and is unlikely to be a real world use case.
So unfortunately the dev said it will take too much effort to fix and that they would include that warning in the next version to make it clearer.When I disabled the macro MD generated a warning message - see the attached system log. I didn't get a warning message when the timeout was set to continue.