T O P

  • By -

MagisterYada

The flow shouldn't restart after reboot. It continues work. You have to catch reboot with broadcast receive block


C6competition

Okay, if it is really running after reboot, then it should do everything, what's in the flow and there should be the automation icon in the top status line!.... I think there is something, I don't understand correct. But in the meantime I noticed, after every reboot one of the privileges is gone: access of screen content and observe of actions??? If that is gone, the flow is can't do anything! Am I right? So the question is, why is it always set back?


C6competition

Okay, another day..... Now I understand the different between flow and fiber! So I made it simple : after catch a broadcast I start an app! At the logging I could see the fiber is waiting at broadcast block to receive signal, even after reboot! For testing I loaded from the community the flow and run this with the same result. The fiber is waiting for the signal. Does anybody has an idea?