Is there a limit on how many days a flow can be active?

[Curtis Pogue]

I have a flow that silences my phone in the morning until I turn on notifications, this runs on weekends only but being on vacation this week I turned it on for everyday.  Twice this week the flow has allowed notifications to come through.  I turned on logging to see why and checked last night that the flow was running.  This morning I got a notification, checked the flow and it was stopped, checked the log and saw this.

07-07 00:00:00.221 I 77@0: Stopped at end

The flow runs as expected but seems it has a time limit.  I so far have not paid for the app, is this a restrictions of the free version?

[Henrik "The Developer" Lindqvist]

"Stopped at end" means the flow reached an unconnected dot/circle, e.g. a NO path going nowhere.

The free edition only has a single limitation, a maximum of 30 running blocks, otherwise there's no difference from premium, see:

https://llamalab.com/automate/doc/premium.html#free_edition

[Curtis Pogue]

That's the thing, no unconnected dots, and it works for 3-4 days straight and then stops.

[Henrik "The Developer" Lindqvist]

Hmm, the 77@0 is a bit odd, since there can't be any block #0.

Can you tell which block it was at before the end, i.e.any block before it with 77@<block number>?

Does the flow use the Fork block anywhere, if so is the "Stop with parent" enabled or disabled?

[Curtis Pogue]

I assume it was on the first block all I have is the one log file I posted on the original post. Here's a screenshot attached to the entire flow maybe you can tell something from this?

[Henrik "The Developer" Lindqvist]

The block numbers seems to be corrupted somehow, as one block as #0 and two with #1?

Anyhow, the NO path of the "Time window" block is not connected, therefore the flow will stop at the end of the time window.

[Curtis Pogue]

I thought you only needed to have something on the no block if you had something you wanted to do if it failed. None of my flows are set up with anything on the no block. What do you suggest goes there?

Curtis J. Pogue
curtis...@gmail.com

--
You received this message because you are subscribed to a topic in the Google Groups "Automate" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/automate-user/sKoge9WrM3A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to automate-use...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/e77ace4f-7aef-420f-a78b-680c6afdcfb4n%40googlegroups.com.

[Henrik "The Developer" Lindqvist]

Generally if you don't want an decision block to do anything on either YES or NO, then you could just make that path connect to IN.

But in your case this makes the use of a Time window block rather pointless, so it should should be replaced with an Time await block instead.

[Curtis Pogue]

Thanks for the reply, I'll take a look at this as it failed on me again this morning. It's odd how it runs for a couple days and then it fails. Thanks for your help!

Curtis J. Pogue
curtis...@gmail.com

To view this discussion on the web visit https://groups.google.com/d/msgid/automate-user/2e94c19e-317b-4a15-8c74-18f801c1698fn%40googlegroups.com.