Hi all - we’re noticing some strange behavior on flow run links that are being generated in Prefect Cloud. Some flow runs have a URL pattern of:

<https://app.prefect.cloud/account/ACCOUNTID/workspace/WORKSPACEID/flow-runs/flow-run/FLOWRUNID>

while others use:

<https://app.prefect.cloud/account/ACCOUNTID/workspace/WORKSPACEID/flow-run/FLOWRUNID>

Where the first example has

flow-runs/flow-run

and the second just uses a

flow-run

format. Some of our users get a 404 error on all links of the first type, and others get 404 on all links of the second type. Does anyone know what might be happening or how to fix this?

I believe we may have fixed this in the most recent release, are you on 2.6.0?

Would this be dependent on the version that the image the flow is using, or the version of Cloud?

Great question! It depends on the change. If you’re on 2.6 that’s helpful. I’ll see what I can dig up…

Hey! We updated the url logic in Cloud around 6 pm EST yesterday. All notifications should now be using the correct format,

<https://app.prefect.cloud/account/ACCOUNTID/workspace/WORKSPACEID/flow-runs/flow-run/FLOWRUNID>

as the url pattern. We did a rolling update so you may have noticed a time period where both url formats were generated. Old notifications will still have the incorrect url. Cloud fully controls the url, so this should not depend on your client version. Sorry for the confusion here!

Thanks for confirming Michael and Zach. The last time we saw a URL with the previous version (just

flow-run

) was 5am PST this morning - is that expected with the rolling update?

@Ilya Galperin Can you try triggering a flow now to see if it's currently working for you (e.g. if you have notifications on Failed state, run a simple flow that raises an error)? this would let us check this easier than looking at timestamps and converting time zone differences 😄

@Anna Geller / @Zach Angell this is from just now, it uses the old URL version and is giving my user a 404 when clicking:

Interesting, I tried that now and couldn't replicate. Are you sure you are on the latest version? Perhaps one component is using an old Prefect version?

Ah I see what’s happened. Looks like one piece of our infrastructure was still running using outdated settings for this. We’ll have it resolved today. Thanks for the report!

Thanks Zach, it looks like this is resolved for us now 🙂