Delay in Timeout of Notification Action block

[Keith]

I'm running Automate 1.31.2 on Android 8. I have a flow that uses the Timeout of the Notification Action block as a timer. If the notification action buttons are not pressed within the specified time, the flow should proceed to execute some other blocks.

However there was severe delay (up to 7 hours) before those subsequent blocks were executed. The delay seemed to be cumulative - if several notifications are waiting for actions at the same time, the ones with later timeout will have more severe (or equal) delay than those with earlier timeout.

I'm currently using a fork and a delay block as workaround, which works fine, so this is no real problem for me now. Just thought I'd report the issue here.

[Henrik "The Developer" Lindqvist]

The Timeout option use "regular" timers, same as system use for its timeouts, e.g. of notifications, network connect/read timeouts, etc., those aren't very accurate, especially if the app is "power save" throttled, or the device goes to sleep.

I'm hesitant to rework such timeouts, e.g. in the Notification action block, to rely on the "Timer accuracy workaround" option (see setting), since there's may other system APIs i would be unable to apply it to anyway.

But i'll update the documentation with a notice of the inaccuracy.

[​ ​man]

Has anything changed since? I just encountered same issue and am looking for a solution. I don't see any notice of the inaccuracy in the docs https://llamalab.com/automate/doc/block/notification_action.html so I thought it was fixed? 

[Henrik "The Developer" Lindqvist]

No change. I need to find some way to automatically replicate the notice throughout the documentation since it will be included in some many places.