Daily cron workflow silently didn't run today

[sumul]

I have a somewhat critical Cron workflow that runs every day at 07:59 UTC. For months it has been reliably triggering itself within a minute or two of the scheduled time, which is great. Today, it didn’t run. There was no error or anything.

In the screenshot, the latest execution (Today) was one I triggered manually after I discovered the issue.

Urgent question: is there any reason I should or should not expect this workflow to resume working tomorrow?

If this is unexpected but also might happen again in the future, what should I do as a backup plan?

[pierce]

Hi @sumul

First off, welcome to the Pipedream community. Happy to have you!

Can you share the URL to your workflow with this issue?

The cron scheduler might have a few minutes of latency but it shouldn’t be skipping scheduled runs altogether.

[sumul]

Thanks! Big fan of Pipedream overall so far.

Here’s the workflow URL: https://pipedream.com/@/p_YyCr1om/inspect

Appreciate your help.

[pierce]

Hi @sumul

Awesome glad to hear it and thanks for your patience on this.

About 2 hours ago (21:00 UTC) a major change to improve reliability and timing of scheduled workflows was just launched.

Please let us know if you see a missed run again tomorrow, but we’re hopeful this should resolve it.

Note: this upgrade does not affect v1 workflows. It will only improve v2 workflows.

If you haven’t already, migrate to v2 for these and other improvements.

[sumul]

Sounds good, thanks for the follow-up!

How can I tell if my workflow is v1 or v2? I don’t see anything about that in the settings, etc.

[pierce]

Good question, it’s not so apparent.

But here’s an example of a v1 workflow. The inspector and builder are essentially in the same view:

And here’s a v2 workflow. The building experience is separate from the inspector:

[sumul]

That’s helpful, thanks. Mine is v2.

[sumul]

This happened again today!