Hi I'm running into an issue with the submit flow ...
# prefect-cloud
m
Hi I'm running into an issue with the submit flow run page crashing when I select custom run and then try to toggle to 'Use JSON Input' instead of the form input. The entire page crashes and I can't enter anything, is anyone else having this issue
c
I am having this issue here ^ Where the command input for the JSON is not populating and I cant change the parameters.
c
Can either of you provide a minimal reproduction of your parameters? I tried a few different things to reproduce this but not seeing any issues with the json in my tests. Forms can be very specific to the parameters so its quite possible its just something different with your parameters than my parameters I'm testing with.
c
Well for me, I cant change any parameters of any flow, they just show up as blank. When I inspect the page, I do see them included in the network request. Also, my entire page then freezes until I hard refresh it.
c
Interesting 🤔 are there any js errors in the console when the page freezes?
And is this in cloud or open source prefect?
c
prefect cloud
I don’t see any errors appearing, if I try to click on anything in the hamburger menu nothing works until I refresh the page.
🤔 1
c
Can you let me know what browser? Also, a long shot but can you try an incognito window with extensions disabled?
c
I did try that, same issues happen. Google Chrome
thank you 1
c
Sorry this is happening. When the page freezes. Does the network tab show requests being made? I wonder if there’s a runaway request that’s being made again and again
c
So nothing is really linking to anything
c
Hmm so looks like you can interact with things already on screen (the advanced options and start sections). But nothing else 🤔
c
correct, I can also start the flow, but I cant change the parameters for it
I do see those in the network request though, for what I originally set them to in the python script its looking at for the flow
👍 1
c
I’m surprised there isn’t a js error in the console. The page as definitely crashed
c
Yeah I didnt see anything super glaring
m
this is what I see when I click "Use JSON Input"
c
image.png
Yeah looks like we have the same issue
c
That’s helpful. @Moxit can you scroll up and show me the first error? Says there’s 34 errors. Curious if any of them are different
m
Screenshot 2024-09-10 at 2.26.01 PM.png
Screenshot 2024-09-10 at 2.26.16 PM.png
c
Hmm okay, I’ll see if I can figure out anything here. But so far unsure
Last question for now. When did this start happening? Was this working until recently? If you have a gut feeling for days/weeks that would be helpful for me to track down what changed.
m
Yeah, I was doing this without any issue yesterday
c
It started for me today
1
#rollback
c
ah okay that's helpful, I'll try and see what was released that might have effected this
m
We're having the same issue: https://prefect-community.slack.com/archives/CM28LL405/p1726039232290819 Was working yesterday at least until approximately 5PM CET.
d
Same issue here. Unable to change any params and in fact lose the ability to click on any buttons on interact with the page. I have to force refresh to get back to the a usable page
Other behaviour: Once the page freezes, clicking the menu sidebar options changes the url in the address bar but the UI stays frozen on the Deployments page
c
Hi folks. In the past hour, we rolled back the deployed version of the Prefect Cloud UI. unfortunately we haven't been able to reproduce this issue ourselves so we're still trying to track down the cause of the issue. atm it seems deployment/flow-specific any additional, disclosable info like parameter types / flow signatures would be helpful. or also if anyone that experienced this issue could help verify that the rollback resolved it - that would be helpful. thanks!
d
Rollback resolved it!
❤️ 1
thank you 1
c
Just to follow-up, we just pushed and released a fix forward for this in Cloud. there was a sneaky bug related to rendering the form for a flow run with a parameter without an explicit type hence the flow-specific nature of this bug. Thanks for y'alls patience and sorry for the inconvenience here. let us know if you're still having similar, related trouble now that we've rolled back forwards.
🎉 3