Issue with TimeControls getting stuck

I have these TCs running every day. However yesterday I noted it seems the TC execution got stuck for 2 of them? Below screenshot is from today, so it is weird these do not show the correct future time, also note the 1 min difference bw. Last Ran & Run At ...

I now modifed and saved both and it seems they got "restarted" and now show the future date correctly. Hopefully that did not destroy the evidence :) but you have below screenshot anyway.

Hope someone can figure out what made these get "stuck"?

Answer 1

[Vinod]

We'll take a look on the back end why these Time Control got stuck. Typically when I have seen this, it is because something has errored out during its previous execution. Maybe your MATLAB code associated to the Time Control timed out, or a ThingHTTP associated with the TimeControl didn't complete. When Time Controls or Reacts running MATLAB code fail, they can be configured to send an email that can give more info.

PS: The "Last Run" column is when the timecontrol last ran. "Run At" is when the next execution of the timecontrol is scheduled for.

Answer 2

[Kolbe Thomas]

Thanks for the help Vinod!

I am lost, it seems to be happening now on all but one TCs? I would not expect to ever have the same date on 'Last Ran' and 'Run At' for a daily recurrence ...

These TCs all only are calling a TalkBack. Nothing is in the queue so not sure why they get stuck?

@Vinod

[Vinod]

@Kolbe Thomas: Could you try editing your timecontrols that are stuck and setting them to run at the next timeslot, but at the top of the hour. So, schedule them at 5:00 AM, 1:00 AM, 6:00AM, etc.

[Kolbe Thomas]

@Vinod done

[Kolbe Thomas]

@Vinod

Seems like full hours made no difference, all but 2 stuck again?

[Vinod]

From investigation on server side, it turns out that some TimeControls that are set up incorrectly are sporadically blocking re-queuing of recurring TimeControls. This is why some recurring TimeControls appear to be working fine while others get stuck.

We're developing a server side fix for this issue that will require no changes on your part as your TimeControls appear to be set up correctly. I will post on this thread when the fix is deployed.

[Vinod]

@Kolbe Thomas: A fix was deployed earlier today. Your TimeControls should now run on schedule. Please let us know if you see errors.

[Stefan]

I observed the same issue. I have one TC running, triggering an action once a day. Last time it got stuck and had to be renewed was after your fix (5th Dec).

The Mathlab code is not really complicated or has high ressource demands, so timeouts seems to be not very likely.

But as a newbie at ThingSpeak I am happy to get advice if I can make it more reliable.

Best Stefan

[Vinod]

@Stefan: From what I see on the backend, your timecontrol seems to be fine. I'm not sure if that is because you had edited and resaved it. In any case, if you see it stuck again, please do not edit it and let me know so we can investiagte. Thanks!

[Stefan]

Hi Vinod, thanks for checking. Unfortunately it happened again, Monday morning it again refused to execute. Also a mail was not sent, I hope I have configured my mail address at the right place…

Thanks in advance

Stefan

[Vinod]

Hi @Stefan: We've been looking at the backend, and I see the TimeControls are executing as expected. If you still see issues, can you please create a new thread?

[Stefan]

Hi Vinod, indeed, the TC turned back to expected operation without any intervention. But on Dec 9th it made a break. Do you want to check those logfiles, if there is any indication why ir did not execute at that day?

Stefan

[Stefan]

UPDATE 17.12.: it seems that also today the script was not running. Again without email notification.

[Stefan]

Update: 18.12 & 19.12. It worked (I did not touch it). Seems that occationally the execution is not started or fails, without sending a mail.