@Marvin This weekend our prefect 2 runners crashed. we rebooted the server and got them up and running again, but the flows now crash and all we get is this error

"resource": {
    "prefect.resource.id": "prefect.flow-run.04d22a99-5e3c-4a1d-b8f9-271924c9da2e",
    "prefect.resource.name": "mu799-prakal-manifold",
    "prefect.state-message": "Flow run infrastructure exited with non-zero status code 3221225794.",
    "prefect.state-name": "Crashed",
    "prefect.state-timestamp": "2025-01-21T11:24:55.322460+00:00",
    "prefect.state-type": "CRASHED"
  },

The error code

3221225794

typically indicates an issue related to system-level problems, often associated with memory access violations or other low-level faults. Unfortunately, there wasn't a direct match in the Prefect GitHub issues or documentation for this specific status code. However, here are some general steps you can take to troubleshoot and potentially resolve the issue: 1. Check System Resources: Ensure that your server's memory and CPU resources are not being exhausted. This error can occur if the system runs out of memory or other critical resources. 2. Review Logs: Look into the detailed logs of the Prefect agent and the flow runs to identify any specific errors or warnings that occurred around the time of the crash. 3. Environment Dependencies: Verify that all necessary dependencies and environment configurations are correctly set up for your Prefect flows. Sometimes, after a reboot, certain environment variables or configurations might not be restored properly. 4. Prefect Version & Updates: Ensure that you are using a stable version of Prefect 2.x. If you recently updated Prefect or any related dependencies, consider rolling back to a previous version to see if the issue persists. 5. State Change Hooks: Consider implementing state change hooks to manage infrastructure cleanup and gain insights into flow run states. This can help manage resources better and provide additional logging for crash scenarios. Learn more about state change hooks. If these steps do not resolve the issue, you might need to delve deeper into the specifics of your infrastructure and possibly consult with Prefect support or community forums for more tailored assistance.

We are on prefect 2.10.13 today - is there something that could have changed in prefect 2 server that is keeping us from running our flows?