Frequently asked questions
Flow made device inaccessible
See safe mode (device recovery).
Premium no longer working
Verification of premium ownership may fail if there’s a problem communicating with the Google Play Store app, try rebooting the device.
See premium page for further information.
Excessive battery usage
The background service responsible for running the flows shouldn’t use much battery.
However, editing flows often on the flowchart screen do use more battery. Reset the battery statistics, don’t use the graphical user interface for a while,
then check the statistics again.
Also, if your flow has a loop in it, make sure there’s a “When …” block somewhere (see Proceed option),
otherwise it will run continuously.
Flow keeps stopping
A flow should only stop if an error occurs, or you explicitly stop it.
Remember that in order to keep a flow running, the last block has to be connected with a path back to the beginning creating a loop.
A flow will stop when it reach an unconnected dot.
I can’t uninstall Automate
Apps that are enabled as Device administrator can’t be uninstalled until disabled.
Disable it in Automate settings
or the system Device administrator settings.
I can’t install permissions
Automate will install permission contained within it’s own package (apk) if Unknown source is enabled in your phones security settings.
If the Install button doesn’t respond in the package installer app, try disabling all screen filter apps used to lower the brightness,
as they may interfere with the button.
I can’t restore backup
- If you can’t restore an Automate backup stored on the SD card. Remember that Automate, by default, can’t access the SD card.
Grant access by enabling/installing the Storage permission in the Manage permissions settings,
before restoring the backup.
- If you open a backup file from within another app like Google Drive, that app may send the wrong file type.
Automate will then fail with an “Corrupt flow” error as it tries to import the file as a flow.
Always use the Restore backup option in Automate settings.
- If the backup file are disabled in the Google Drive app,
it usually means there’s a MIME type issue.
Long-tap the file and choose Download, then restore the downloaded backup file instead, it’s located in the “Downloads” directory on the SD card/Internal storage.
If a flow stops working, with an “Failed to read…” error after you’ve upgraded to a newer Android version, you’ll have to reconfigure
all the App start shortcut and Plug-in blocks.
This happens when Android has changed its internal data format.
Crash when starting flow
If Automate crashed when starting a flow, try increasing the stack size in
The Automate “running” notification
The Automate “running” notification must be showing because Android require it to keep a background service running, without it Automate would become very unreliable.
Disabling notification for Automate in the device Apps settings will prevent all notifications from showing, including the Notification show block,
it may also prevent the Toast show block from displaying “Toast” messages.