@Marvin i find that deploying deploying flows with

<flow>.build_from_source.deploy

to our self hosted server on prefect 3.1.1 fails whenever i add any from of schedule via the

cron

or

schedules

parameters:

Response: {'exception_message': 'Invalid request received.', 'exception_detail': [{'type': 'extra_forbidden', 'loc': ['body', 'schedules', 0, 'max_active_runs'], 'msg': 'Extra inputs are not permitted', 'input': None}, {'type': 'extra_forbidden', 'loc': ['body', 'schedules', 0, 'catchup'], 'msg': 'Extra inputs are not permitted', 'input': False}],

It seems you're encountering an issue with scheduling in Prefect 3.1.1, where you receive errors related to forbidden extra inputs such as

max_active_runs

and

catchup

. This appears to be part of a known challenge with defining schedules in deployments. The error mentions "extra inputs are not permitted," which indicates that the Prefect server doesn't recognize or allow these parameters in the way they are being specified. The issue might be related to a mismatch between the client and server expectations for deployment parameters. Here are a couple of potential solutions: 1. Verify Schedule Definitions: Ensure that your schedule definitions in the flow deployment are compatible with Prefect's expected input. For instance, Prefect supports specific schedule types such as Cron, Interval, and RRule. You can find more information on how to define these schedules in the Prefect 3.x documentation. 2. Check Parameter Compatibility: Based on similar issues reported, it seems some parameters, like

catchup

and

max_active_runs

, aren't part of the standard schedule schema, which might lead to a "422 Unprocessable Entity" error as detailed in issues on GitHub, such as DeploymentApplyError and others. Review your input parameters to ensure they align with what's supported in the Prefect API. 3. Update Prefect: Consider checking for any updates or patches that may have been released after 3.1.1. Sometimes, pending bugs are resolved in later patch updates. Feel free to reach out if you need more assistance or delve deeper into a specific part of the deployment process — I assure you it's not because I've got nothing better to do! 😄

The issue might be related to a mismatch between the client and server expectations for deployment parameters.

yeah it is what version are you running?

ahh, for the server

3.1.1

, for the client

3.0.11

can you update the client?

bentoml prevents me doing that atm 😕 do you think that would resolve the issue?

👍