I upgraded Prefect from 2 6 5 to 2 7 2 this morning and now

Question

I upgraded Prefect from 2 6 5 to 2 7 2 this morning and now many or maybe all of our flows are failing We have a local Prefect instance running flows locally not connected to Prefect cloud I logged an issue here which explains the details with error logs <https github com PrefectHQ prefect issues 7922> This is our production server so any clues on how to get us back online quickly would be much appreciated Thanks for the great software and for the help

Ryan Peden · Answer

Hi Richard rolling the database back should be possible if you want to go back to 2 6 5 for now Since it is your production database I advise making sure you have backups as a precaution though I don t expect any issues You should be able to roll back to 2 6 5 by running ```prefect orion database downgrade r 3ced59d8806b``` See <https prefect community slack com archives CL09KU1K7 p1667858992768019|this thread> for additional details

Jeff Hale · Answer

Thank you for raising The <https github com PrefectHQ prefect pull 7920|PR fix> is open and we expect to release 2 7 3 soon

Richard Alexander · Answer

< Ryan Peden> thanks so much Downgrading the database workd perfectly I just didn t know how to do it You saved the day smile

Ryan Peden · Answer

Glad to hear it helped slightly smiling face

Richard Alexander · Answer

< Jeff Hale> so is my flow name the underlying issue Is that why my issue is related to the refenced PR

Richard Alexander · Answer

< Ryan Peden> sorry to bother you again but I m trying to understand the downgrade process just in case I need to perform it again in the future I m unclear on how you found the proper revision to send me I did the following Went to the reference thread Went to the postgres revisions page on github I see that the revision ID is listed both inside the files and within the filename But I can t find the revision ID that you sent How did you determine the correct revision for my specific case of downgrading to 2 6 5

Ryan Peden · Answer

The link in that thread is to 2 6 4 I changed the URL to 2 6 5 <https github com PrefectHQ prefect tree 2 6 5 src prefect orion database migrations versions postgresql>

Ryan Peden · Answer

and then went down to the bottom to find the newest migration

Jeff Hale · Answer

re flow name yes there was a bug with parsing function and flow names

Richard Alexander · Answer

Ah Perfect thank you I didn t notice it was on the wrong branch