Switching schedule causes Parameter Overrides to be lost

[tomcatu]

Bug summary

Switching schedule causes Parameter Overrides to be lost

Version info

Version:             3.2.6
API version:         0.8.4
Python version:      3.12.8
Git commit:          5ceb3ada
Built:               Wed, Feb 19, 2025 9:24 PM
OS/Arch:             darwin/arm64
Profile:             ephemeral
Server type:         server
Pydantic version:    2.10.6
Integrations:
  prefect-aws:       0.5.3

Additional context

No response

[joshcaskie]

I believe my scenario is also related. I use

prefect --no-prompt deploy --prefect-file deployments/prefect.yaml --all

as part of an automated deployment process.

The first time a deployment is created, the parameter overrides are successfully propagate.

If I then delete those schedules manually from the UI, and attempt to re-run my deployment script, the schedules are created again but they don't have the overrides.

The only way to get the overrides BACK through my script, is to run the prefect deploy command a 2nd time, which then causes the overrides to return.

Hoping this bit of additional context is related and can be addressed soon. Doesn't impact too much for my process, but now I know if I am testing and need to update the schedules, the entire deployment has to be deleted first, before re-deploying, to ensure the proper parameter overrides are passed and set correctly.

Prefect 3.2.11

[joshcaskie]

A quick follow up to the tests mentioned in the Issue: activating and deactivating a schedule.

I don't see my parameter overrides getting deleted, but the slug does get deleted, which still indicates that there's an issue with something here.

Thanks!

[tomcatu]

It's not that the parameters are overwritten, that the parameters are cleared.

[joshcaskie]

Correct @tomcatu. I'll amend my statement that I'm also witnessing the parameters and slug names clearing in various circumstances.

It makes me think something with the Cloud UI "Update schedule" API is not configured right with the new Parameter Overrides or what not, but that's just my suspicion.

[zzstoatzz]

hi @tomcatu and @joshcaskie - thanks for the info. can either / both of you share a minimal example deployment where this occurs for you? in cases where you hit this, are you using prefect deploy or other ways to create deployments?