Anna Geller12/15/2022, 10:44 PM
argument to the
utility to gracefully stop the infrastructure process and put the flow run back into a
state. This way, you can free up the infrastructure resources instead of keeping the original flow run process running while waiting for approval.
💡 Note that: this kind of rescheduling pauses works only with flow runs created from deployments and requires results persistence using either theYou can now also manually pause a flow run in progress using the new Pause button directly from the flow run UI page (see the screenshot below). Resuming a run can be performed also from the UI, or from code:option on the flow decorator, or by setting it globally:
prefect config set PREFECT_RESULTS_PERSIST_BY_DEFAULT='True'
Other enhancements and improvements in this release: • Two new Prefect Collections: prefect-kubernetes :kubernetes: and prefect-bitbucket :bucket: • Task Run Concurrency UI page now includes details and shows active task runs currently using allocated concurrency slots (see the second screenshot) • New Opsgenie notifications block - kudos to Julien Lutran for contributing! :gratitude-thank-you: • Fixes to imports and their performance • New
from prefect import resume_flow_run, pause_flow_run id_ = "pasy_your_flow_run_uuid_here" pause_flow_run(id_, timeout=4200, reschedule=True) # once you're ready to resume (you can do it from the UI, too): resume_flow_run(id_)
block field that allows to obfuscate nested values in a dictionary on blocks such as
• If you have a flow call (e.g.
) in your flow script, not protected by an
block, any run from that deployment will now work without giving you a warning about that unprotected call • Several documentation improvements incl. new
if __name__ == "__main__:
usage examples, recipe and tutorial references, Automations docs, and more! For all enhancements and fixes, check the release notes - it even includes a Marvin joke. :marvin-duck: Happy engineering! 🎄😛refect-duck: