@Marvin After bumping the version from 2023.07.13 to 2024.4.18205353 started to observe crashes:

No such command 'execute'.

is it a known issue?

It seems there are no open GitHub issues specifically mentioning the error message "No such command 'execute'." However, Prefect 2.x has gone through significant changes, and it is possible that a breaking change or a regression might be causing your problem. The latest Prefect version as of the information I could gather is 2.18.0, which includes several breaking changes, such as removal of deprecated CLI options and abilities related to deployments. These changes might impact the way commands are expected to be executed, depending on the scripts, third-party tools, or custom Prefect CLI wrappers you may be using. As a first step, I would suggest checking if there are any recent changes to the deployment process that might affect your usage. Cross-reference your current workflow against the Prefect 2.18.0 release notes and consult the Prefect documentation for information on deprecations and migrated functionality. For more in-depth investigation, especially if it is an undocumented issue, consider raising an issue on the Prefect GitHub repository with relevant details such as stack traces, reproduction steps, and how your upgrade process was conducted. This can help the Prefect community and developers address your concern more effectively.

this is an indication that your worker and your flow execution environments are too far out of sync. upgrading prefect wherever your flows run should fix this