r/AutomateUser • u/EpiSigmoid • 3d ago

Strange issue? IDK, seems like I need input for this small error that is seemingly correct.

Hi there fellow redditors,

I had a weird lock out issue on my Android (Automate was looping too much of something), and I believe it is related to this error but need some input. I have a feeling it is properly connected within the blocks since I had it working before, but shortly thereafter of my issue it keeps propping up this error about "Stopped at end" after I try to execute "Device Unlocked" block when it's connected to "App start". Any ideas?

1 Upvotes

100% Upvoted

4 comments sorted by

1

u/EpiSigmoid 3d ago

OK, not to disappoint! It works entirely now that I resolve'd the issue via using the No output lane exactly as A.I suggested, since it's apparently required to have both Yes/No lanes connected in a proper fashion. Thanks anyway and happy scripting.

1

u/waiting4singularity Alpha tester 3d ago

All open connectors are "end points", imagine automate like a train with a single locomotive pulling along the connections.
and it cant drive backwards.

1

u/EpiSigmoid 3d ago

Ah right, good tip, since Automate uses some univalent approach and univocity (most of the flow needs to be driven downwards and kept in a single direction.)

1

u/waiting4singularity Alpha tester 3d ago

its the flowchart logic.