Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

prefect_flow_run_job_variables.png

Hello, I'm using prefect version 2.18.3. I'm trying to override job variables for a deployment flow run <https://docs.prefect.io/latest/guides/deployment/overriding-job-variables/#using-the-custom-run-form-in-the-ui> but I don't have the option in the ui ?

Thanks for flagging <@U07187VG5JR> - I don't see it either. I'm going to take a look into it!

This should be fixed in yesterday’s release <@U07187VG5JR>. Thanks for flagging and please let us know if you run into other issues. 

Hello, yes I see it now with the new release, Thank you

hi <@ULXMV9SD7> which release was this fixed in?
i'm having the same exact issue with version 2.19.5 deployed locally using helm
<https://github.com/PrefectHQ/prefect-helm/releases/tag/2024.6.13185354>

Hi <@U05FP7DBH0U> - I’m afraid I don’t know the release number off the top of my head. I’d expect it to be before 2.19.5 though. Can you give me more information about what you’re actually seeing? 

In the screenshot you sent here (<https://prefect-community.slack.com/archives/CL09KU1K7/p1719154686136319|https://prefect-community.slack.com/archives/CL09KU1K7/p1719154686136319>), the additional options section looks untoggled. Can you open that section and send a screenshot of what you’re seeing? 

image.png

here is with additional options
seems that they are the generic additional options

Screenshot from 2024-06-24 11-11-57.png

by the way I see this error in the browser console:

Ohhh I’m sorry. I didn’t read your second message closely enough. This is a different thing to what Louise reported. 

This thread is about defining job variables - which are right there in your drop down. 

On closer reading, your concern is about how your parameters show up? That’s likely from an update on how we handle parameter schemas. 

We use pydantic as our base - <https://www.prefect.io/blog/what-is-pydantic-validating-data-in-python?gad_source=1&amp;gclid=Cj0KCQjwsuSzBhCLARIsAIcdLm4cpR4RlUUHntnWiWNNDBmLfO0CCFzDeidyGhKpUhVU7_xOpiFbDXYaAnDBEALw_wcB|https://www.prefect.io/blog/what-is-pydantic-validating-data-in-python?gad_source=1&amp;gclid=Cj0KCQjwsuSzBhCLARIsAIcdLm4cpR4RlUUHntnWiWNNDBmLfO0CCFzDeidyGhKpUhVU7_xOpiFbDXYaAnDBEALw_wcB>

You can see more about the best way to represent parameter types in the pydantic docs. 

<https://docs.pydantic.dev/latest/|https://docs.pydantic.dev/latest/>

I see that the versions changed from pydantic 1 to 2
maybe that caused the error
I will take a look tnks