Hi all, is there a good way of deleting flows. Try...
# ask-community
s
Hi all, is there a good way of deleting flows. Trying to delete a flow gives a popup error:
We could not delete your flow. Please try again. If this problem continues, contact <mailto:help@prefect.io|help@prefect.io>
c
Not that I have a solution, but just pinning this https://docs.prefect.io/api/latest/cli/delete.html as it probably would be handy to have the option to delete flows via the CLI
👍 1
s
Yeah, adding flows would be useful, I cant even delete my project using the cli, because I get a
Read timed out. (read timeout=15)
😞 EDIT: On the sixth attempt the project was deleted and I reuploaded all flows
😬 1
j
Hi @Samuel Hinton - Looking into this one for you. Did you manage to delete your flow or are you still experiencing problems with it? If you're still experiencing problems, would you mind sharing the flow id? (You can DM it to me if you'd rather.) Also want to check - were you deleting just one version of the flow? Or all versions? Thanks!
s
Hi Jenn! 🙂 I dont have the ID on me, eventually I got the project to delete itself and then reuploaded the flows (this is all on prefect server btw). I was deleting all versions. I had thought that maybe the whitescreen issues (in the next post I made) might have been caused by a misbehaving flow so thought Id delete just in case. Alas, it was not the flow.
j
Just about to respond to your white screen post! We actually updated the delete flow button not long ago so I'm surprised it wasn't behaving. I'll flag that with the team to see if anyone has ideas. Please let me know (with the flow ID 🙂) if you see it again. - Edit: Ah actually - just realized the flow id isn't going to help much as you're on server. 🤦‍♀️
s
Will do 🙂
👍 1
v
Hi, I'm having the same error message
We could not delete your flow. Please try again. If this problem continues, contact <mailto:help@prefect.io|help@prefect.io>
, when trying to delete flows from my UI on a solf-hosted server, but a few minutes later the flow is removed from the UI. So it looks like it's working in the background after the error message is shown, and it still gets the job done.