Problem with "Wait before next action"

[Lupus52]

Hello, I write or change some little macros for my new car android 10 unit.

Problem: Between two calls of a action I use

"Wait before next action" with 5 seconds

This worked in all nearly 100 macros I wrote in the last years for my many devices.

Now the macro stops completely at this point. Any more actions don't run.

I tested some time and I found a problem in the old forum with nearly the same problem

There 5 second and more did not work, but 4 seconds 490 ms and less worked.

I tested it now on my equipment

I tried this in my macro and I have the same result!

4.990 Seconds work and 5.000 seconds bring the macro to stop.

It does not matter if the [ ] use scheduler is activated or not.

In the systemprotocol I find: (see picture)

"Failed to resume macro after wait before next, if was -1"

Ok - I used some hours to find and locate this bug in my macros. I copied a lot from my old device and no one worked correctly :-(

And I can do a workaround with repeated calls of a shorter macro.

But I think that many people will struggle over this bug, and therefore it should be fixed soon

 

[tanutanu]

Hello, I write or change some little macros for my new car android 10 unit.

Problem: Between two calls of a action I use

"Wait before next action" with 5 seconds

This worked in all nearly 100 macros I wrote in the last years for my many devices.

Now the macro stops completely at this point. Any more actions don't run.

I tested some time and I found a problem in the old forum with nearly the same problem

There 5 second and more did not work, but 4 seconds 490 ms and less worked.

I tested it now on my equipment

I tried this in my macro and I have the same result!

4.990 Seconds work and 5.000 seconds bring the macro to stop.

It does not matter if the [ ] use scheduler is activated or not.

In the systemprotocol I find: (see picture)

"Failed to resume macro after wait before next, if was -1"

Ok - I used some hours to find and locate this bug in my macros. I copied a lot from my old device and no one worked correctly :-(

And I can do a workaround with repeated calls of a shorter macro.

But I think that many people will struggle over this bug, and therefore it should be fixed soon

I confirmed the problem, so I put 4 seconds wait action on my macro twice when I need, or use stop watch.
I noticed it around 6 months ago. It didn't happen last year.

 

[Lupus52]

With this bug it seems that there is a following problem caused by the buggy timeservice: After switching power off/on after restart my 3 testmacros were deleted! This happened 3 times. I retyped one macro, tested some times and after next power on/off the macro was killed. (No macros available) In more than 3 years of using MD on different devices, never a macro was killed (deleted).

 

[tanutanu]

With this bug it seems that there is a following problem caused by the buggy timeservice: After switching power off/on after restart my 3 testmacros were deleted! This happened 3 times. I retyped one macro, tested some times and after next power on/off the macro was killed. (No macros available) In more than 3 years of using MD on different devices, never a macro was killed (deleted).

hmm...good tips! I remember it for my next macro. Danke