Will Automate flows pause & resume safely under Android 15 “Optimized” battery mode?

[Alex]

Device/OS

• Samsung, Android 15, One UI 7.0

Goal
Reduce Automate’s power usage. I’m fine with the OS putting Automate to sleep, as long as the flow isn’t killed and continues/resumes normally after wake.

Current settings

1. Android Settings → Apps → Automate → Battery → Optimized

2. In my flow’s settings I have unchecked “Ignore battery optimization”.

Scenario

• I start the flow.

• After the inactivity period, the device goes to sleep/Doze.

• I assume Automate will also be put to sleep by the OS.

Question

• In this configuration, will my flow reliably pause and then resume after the device wakes, without being killed by OS?

[мJ Zкxy]

Yes but if you have broken flow it may make thing worse since it can't stop at all.

[Henrik "The Developer" Lindqvist]

Safe yes, but it will likely break all timing operations like Delay, and Time await/window blocks, and probably lots of other things.

Then there's Samsung's other non-standard Android modifications that break/kill apps when "power saving" is enabled.

Automate should not prevent the device from going to sleep, not unless you've got incorrectly made flows that running continuously, please read: https://llamalab.com/automate/doc/faq.html#battery_usage

[Alex]

My flow is intended to pause while the phone is asleep and then continue when the device wakes up. Specifically, could you confirm that:

1. the OS will not kill the flow while the device is sleeping; and

2. the flow will automatically resume normal operation after the device wakes?

[Henrik "The Developer" Lindqvist]

1. I can't say since it depends on how much the device manufacturer has broken their Android. 
   An app with a "foreground" service should usually only be killed in a low-memory situation then be restarted when that's has passed. 
   Sadly that's not always the case, even standard Android has problems restarting an apps accessibility service.
2. Yes it should, just as any app should do.

You'll have to test yourself, on your device.