Flow only starts when it's open in foreground

[Zauq]

Using version 1.42.4 and Android version 13 Infinix GT 10 Pro.

Everything was working fine but one fine the issue started of flow not executing when in background. It'll work for one instance but not for the other.

The specific flow has to be opened in order to execute it, every power saving setting is off, even tried "Device Keep Awake" block as suggested in FAQ but no avail. 

Uninstalled, reinstalled, rebooted after installation tried everything. I had found to be very useful hence bought the Pro version but now this issue. 

[Henrik "The Developer" Lindqvist]

At which block does the flow get stuck?

[Zauq]

Every block, basically flow starts normally but when it's time to execute the block it does not work unless the particular flow is opened. During this time Automate is running in the background, no issues there. Sometimes in the log I see "resumed after restart" but that's not the case always. In some flows there's no "resumed after restart" but it still does not execute the block unless is opened.

This issue started recently, earlier it was working file.

[Henrik "The Developer" Lindqvist]

Nothing related to how flows are executed has changed for years.

"Resumed after restart" means the app was killed by the system, usually due to some non-standard "power save" feature, ensure to disable them.

As said, maybe be there's a particular block/feature that the flow gets stuck at?

Android version?

[Zauq]

Android Version 13.

I have deleted all the flows and created a very simple flow. The flow starts with a 3 min delay and then as sms sending block to send sms to my other mobile number. However, it didn't send any sms after the delay till I opened the app after 5 mins or so. You can also check the log there was not any "Resumed after restart" in the log this time and yet the simple flow didn't work at all. I have checked time and again all the battery saving options which all are turned off. As I had mentioned, the issue start recently, I didn't this issue earlier using the same phone. Might this be a issue with the update??

04-10 00:09:48.660 I 38@1: Flow beginning
04-10 00:09:48.662 I 38@2: Delay
04-10 00:14:35.085 I 38@3: SMS send
04-10 00:14:35.280 W 38@3: 1 SMS sent to xxxxxxxxxx
04-10 00:14:35.280 I 38@4: Delay
04-10 00:18:20.223 I 38@5: SMS send
04-10 00:18:20.314 W 38@5: 1 SMS sent to xxxxxxxxxx
04-10 00:18:20.314 I 38@0: Stopped at end
04-10 10:18:56.420 I 39@1: Flow beginning
04-10 10:18:56.422 I 39@2: Delay
04-10 10:57:52.796 I 39@3: SMS send
04-10 10:57:52.860 W 39@3: 1 SMS sent to xxxxxxxxxx
04-10 10:57:52.861 I 39@4: Delay
04-10 11:36:42.376 I 39@5: SMS send
04-10 11:36:42.493 W 39@5: 1 SMS sent to xxxxxxxxxx
04-10 11:36:42.493 I 39@0: Stopped at end
04-10 12:05:27.667 I 40@1: Flow beginning
04-10 12:05:27.670 I 40@2: Delay
04-10 12:09:02.671 I 40@3: SMS send
04-10 12:09:02.790 W 40@3: 1 SMS sent to xxxxxxxxxx
04-10 12:09:02.791 I 40@4: Delay
04-10 12:09:11.186 I 40@4: Stopped by user

[Henrik "The Developer" Lindqvist]

Odd. Ensure the Delay block is using Proceed=Exact and that the Awake device option is enabled. 

Sadly there's not much an app can do if the system don't deliver timers accurately.

This shouldn't be necessary on Android 13, but try using an "Timer accuracy workaround" in Automate setting, e.g. "Alarm clock".