@Marvin I am using this so far

test_executor_bkhaneja.from_source(
        source=str(Path(__file__).parent.resolve()),
        entrypoint=f"{Path(__file__).name}:test_executor_bkhaneja",
    ).deploy(Test Deployment", work_pool_name="cla-infra", cron="15 3 * * WED", concurrency_limit=1)

but when I upgraded Prefect today, is it giving 422

The 422 error you are encountering when deploying with

from_source

suggests an issue with the request payload or the server's ability to process it. This could be due to changes in how Prefect handles deployments in the latest version. Here are a few things to consider: 1. Deployment API Changes: Prefect 3.x introduced changes to the deployment API. Ensure that your code aligns with the latest syntax and requirements. For instance,

from_source

and

.deploy()

might have specific expectations regarding arguments. 2. Work Pools and Infrastructure: Prefect 3.x replaces agents with workers and introduces work pools. Ensure that your deployment configuration correctly references these new constructs. Check if your work pool "cla-infra" is properly set up and accessible. 3. Review Release Notes: There might be recent changes or bug fixes that affect deployment behavior. The latest release notes here might provide insights. 4. Documentation and Examples: Refer to the deployment documentation for detailed guidance on setting up deployments with the latest Prefect version. If the issue persists, consider reaching out to the Prefect community or checking GitHub issues for similar problems.