Hello all I recently updated from Prefect 2 1 0 to 2 3 2 Aft

Question

Hello all I recently updated from Prefect 2 1 0 to 2 3 2 After updating I re deployed my existing deployments I am now seeing flows being scheduluded twice I do not see duplicate deployments listed in the UI or API Based on the created dates it appears Prefect is still scheduling using the 2 1 0 deployments as well as the 2 3 2 deployments The old flow runs have null value the deployment id field FYI I am using Prefect cloud Has anyone seen anything like this and or have a recommended way of purging what seems to be previous Prefect deployments still being scheduled

Ross Teach · Answer

``` id ffc2832b 959b 4950 b08f 4a710b850c35 created 2022 09 06T13 11 33 108901+00 00 updated 2022 09 06T13 11 28 970538+00 00 name enormous toucan flow id d3f7aed7 f1a7 4d10 9903 04b7f20bb846 state id 2b539407 f42e 4a5d b047 568b293b6dbc deployment id null work queue name prod flow version null parameters idempotency key scheduled 2f8d28e6 9b39 497f a1cf 9d656b5cd768 2022 10 16T06 00 00 04 00 context empirical policy max retries 0 retry delay seconds 0 0 retries null retry delay null tags auto scheduled prod airbyte google parent task run id null state type SCHEDULED state name Scheduled run count 0 expected start time 2022 10 16T10 00 00+00 00 next scheduled start time 2022 10 16T10 00 00+00 00 start time null end time null total run time 0 0 estimated run time 0 0 estimated start time delta 0 0 auto scheduled true infrastructure document id 56c4c095 188f 4a89 9a6e ccc18eda986b state id 2b539407 f42e 4a5d b047 568b293b6dbc type SCHEDULED name Scheduled timestamp 2022 09 06T13 11 30 485515+00 00 message Flow run scheduled data null state details flow run id null task run id null child flow run id null scheduled time 2022 10 16T06 00 00 04 00 cache key null cache expiration null untrackable result false ```

Anna Geller · Answer

I d recommend either 1 Toggle schedule off and back on 2 Create a deployment with a new name 3 Better remove and recreate a deployment the latest release has an update mechanism so that if you already have a deployment Prefect will only update those arguments that changed rather than doing it in a way that deletes deployment and creates a new one from scratch from the latest config

Ross Teach · Answer

Thank you so likely deleting all my existing deployments and then re creating them should do the job

Anna Geller · Answer

absolutely here is a script that will make it easy ```import asyncio from prefect client import get client async def remove all deployments client = get client deployments = await client read deployments for deployment in deployments print f Deleting deployment deployment name await client delete deployment deployment id print f Deployment with UUID deployment id deleted if name == main asyncio run remove all deployments ```

Anna Geller · Answer

once you run it you have a clean slate and all deployments are gone and you can start from scratch

Ross Teach · Answer

Thank you very helpful I will incorporate this into my CI