Hi guys, I started this flow that works great outside. However, once indoors,it gets stuck because it cannot bypass the locating error.
It gets both net and GPS location an and sends an SMS with current location and emails 2 pictures (front and rear) so you can see the person and the environment where the phone is located.Regarding the GPS toggle, it also displays the" high accuracy.." annoyance, so maybe some of you knows how to get rid of the message as well.Flow reacts to SMS with text "-lost-". You will have to replace Google and Yahoo accounts with your own.
stolen phone flow- locator
Moderator: Martin
stolen phone flow- locator
- Attachments
-
- flow_Anti_theft_20170213_175958.xml
- (9.05 KiB) Downloaded 720 times
Re: stolen phone flow- locator
I haven't opened your flow, but if you're getting an error that you want to bypass, you can do so using an "exception".
Basically, open the flow in edit mode. Look at the action or condition that is generating the error (in this case, maybe something like "Init Variable Location"). Let's call that Item1. It'll already have a line below it, linking it to the next action / condition, which we'll call Item2.
Tap Item1, and it will now show 4 icons. Drag the "+" icon down to join it onto an action / condition that "skips" the location requirement (most probably it'll be somewhere below Item2).
So, now you have TWO lines coming out of Item1; one to Item2, the other to something below Item2. Now, tap the "new" line. You'll see two icons appear: one allows you to delete the line, the other (a pencil) allows you to edit it. Tap the pencil. It'll show "normal" as being checked. Instead, check "exception". Now, that new line will be shown as a red dashed line.
As a wrinkle: depending on how your flow is constructed, it's possible that you may want to link the new line directly to Item2 - that is, to have BOTH a "normal" AND an "exception" connection between Items 1 & 2. In that case, when you try to make the new line you'll get an error saying that "there is already a connection". Easy to get around this: just change the EXISTING line to an exception, then draw a new line, which will automatically be a "normal" connection. I've attached a screenshot of this setup (which I often use)
That's it. Now, when your flow reaches Item1 (so your phone is looking for the location) then if it FINDS the location, the flow will continue as normal; but if it FAILS to find the location then (after the timeout) it'll follow the "exception" line, which also allows your flow to continue.....
Basically, open the flow in edit mode. Look at the action or condition that is generating the error (in this case, maybe something like "Init Variable Location"). Let's call that Item1. It'll already have a line below it, linking it to the next action / condition, which we'll call Item2.
Tap Item1, and it will now show 4 icons. Drag the "+" icon down to join it onto an action / condition that "skips" the location requirement (most probably it'll be somewhere below Item2).
So, now you have TWO lines coming out of Item1; one to Item2, the other to something below Item2. Now, tap the "new" line. You'll see two icons appear: one allows you to delete the line, the other (a pencil) allows you to edit it. Tap the pencil. It'll show "normal" as being checked. Instead, check "exception". Now, that new line will be shown as a red dashed line.
As a wrinkle: depending on how your flow is constructed, it's possible that you may want to link the new line directly to Item2 - that is, to have BOTH a "normal" AND an "exception" connection between Items 1 & 2. In that case, when you try to make the new line you'll get an error saying that "there is already a connection". Easy to get around this: just change the EXISTING line to an exception, then draw a new line, which will automatically be a "normal" connection. I've attached a screenshot of this setup (which I often use)
- Screenshot_20170213-144825.png (73.73 KiB) Viewed 6662 times