Anyone using automated remote actions for Android log collection?Solved

Participant
Discussion
2 weeks ago Mar 03, 2026

We just started looking into the Automate feature for remote actions, specifically for gathering Android bug reports across our logistics fleet. Historically, when a driver reports a device crash, we have to manually trigger a log collection, wait for the device to be online, and then pull the data. By the time we get the logs, the “smoking gun” is often overwritten or the state has changed. 

I’m curious if anyone here is using the scheduling/automation side of this to stay ahead of errors. We’re thinking about scheduling a weekly bug report for our “Beta” device group to monitor stability without manual intervention. Is anyone else automating their log acquisition, or are you still triggering it reactively? 

Replies (1)

Marked SolutionPending Review
Participant
1 week ago Mar 04, 2026
Marked SolutionPending Review

@margaret, we actually moved to an automated schedule a while back, which has been useful for catching those transient bugs that disappear after a reboot. If you wait for a user to report an issue, you’re already behind the curve. 

We set up a scheduled remote action to pull bug reports every Tuesday at 2:00 AM for our warehouse tablets. The key for us was using the Include/Exclude groups effectively. We exclude devices that are currently in high-intensity shifts so we don’t hit the processor while they’re scanning inventory. Having those logs waiting in the portal every Wednesday morning means we find memory leaks before the devices actually lock up in the field. It’s much more reliable than the old “remote in and hope the logs are still there” method. 

Save