Hello! I have two questions: 1. is it possible to ...
# ask-community
i
Hello! I have two questions: 1. is it possible to to set a custom retry logic per deployment? I am deploying using Python to prefect cloud & using AWS ECS & ECR. Marvin suggested
my_flow.with_options(retries=100).deploy(...)
I tested it and I didn't work then Marvin retracted that. 2. (more like a suggestion) it will be nice to see the full name of the deployment and not the dots suffix like
project-1_flow-x_...
(as the name has valuable info for us) or at least have an option to display the full deployment name. Another missing info in the UI from what I could see is flow/deployment options (retry logic for instance because I could only see it in the deployment run - like I have to run it then cancel it just to see the setup retry logic)
n
1.
with_options
will work for subflows, but if you modify the flow object after you deploy it, you wont see those things take effect on the deployment 2. "it will be nice to see the full name of the deployment" where?
i
Thanks Nate for having a look! 1. Got it, thanks! Are you aware of any other way to have separate retry logic per deployment in case I missed something in docs (I also browsed the implementation a bit and it doesn't seem possible with the way it is) 2. I meant in the web UI here are screenshots: (I will be having 30+ deployment for the same flow and the difference in the name is in the last few words which are hidden & replaced by
...
, so basically I have to hover the mouse over each to know which one is that or just open it, while the screen still has a lot of empty space that could fit the full name, this is just something that could improve the UX in my opinion and I could be wrong)
Another thing I wanted to express in my first message: If the retry logic is part of the flow, it would be cool to have this info displayed in the web UI when looking at a particular flow. This info (retry logic) isn't visible in the web UI from what I could see, until I run the deployment. I think this could be very useful when I will be adjusting the retry logic from our python and checking if it took effect in Prefect Cloud.
@Nate ping
n
@Idriss Bellil • please feel free to open an issue regarding the UI name truncation thing • you can always have a more general deployment that employs different retry logic depending on the parameters or other state available at the start of runtime i would recommend making use of deployment descriptions as much as possible to bring information about retry strategies into the ui.
i
Thank you 🙏