Hello We have recently upgraded our Prefect server to the ne

Question

Hello We have recently upgraded our Prefect server to the newest version and experiencing some inconsistency after that One thing is we are experiencing is problems when refreshing a flow page and then met by deployment url 404 I can se that the flow id is GUID 1 on initial load of the flow page and then it changes to GUID 2 after the page has been loaded Check Thread for more information arrow right

Dave · Answer

We tried a completely different machine that hasn t been using the UI yet and its the same is happening we have also tried to remove all the cached data and actually also cleared everything in Chrome Browsers Win10 Edge Chrome amp MacOS iOS Safari System information Server core 0 14 5 UI core 0 14 5 Deployment Note We are running the `prefect server database upgrade y` when upgrading to a different Prefect version we also performed hard refresh in the browsers Console logs ```e6d424aa 0fe1 436e 9b0d af79076eaa9f 1 Access to script at from origin has been blocked by CORS policy No Access Control Allow Origin header is present on the requested resource e6d424aa 0fe1 436e 9b0d af79076eaa9f 12 GET net ERR FAILED```

Josh Greenhalgh · Answer

I have been seeing exactly this behaviour too

Josh Greenhalgh · Answer

Can t help though disappointed

Josh Greenhalgh · Answer

Where are you running everrything

Dave · Answer

Currently running in Linux VM `Linux 5 4 0 1031 azure x86 64 with glibc2 29` using docker compose deployment but I have also tried Win10

Josh Greenhalgh · Answer

I am running on k8s using the helm chart provided by prefect this behaviour seems to generally be tied to failures and restarts of the graphql and hasura services are you seeing similar

Dave · Answer

Ahh cool would go for the helm chart when I have some more time Anyways actually no everything is running great except the inconsistency in the UI I have been running the same setup since 0 12 0 and it started occurring at 0 14

Marcelo Ruas · Answer

< Luciano Fernando Palmeira de Almeida> this is the same issue we were having yesterday

Dave · Answer

Multiple has been experiencing this bug did anybody found a fix

Jenny · Answer

< Dave> would you mind opening a ticket with as much detail as possible ideally a reproducible example in the ui repo Slack messages are harder for us to track UI repo

Dave · Answer

I actually found it you are displaying the Flow Group Id instead of the Flow Id but I will open up the ticket thank you

Jenny · Answer

< Marvin> open Server flow page bug

Marvin · Answer

Jenny · Answer

Wrong repo

Jenny · Answer

< Marvin> open Server Flow Page bug in UI

Marvin · Answer