<@ULVA73B9P> 0%| | 0/100 [00:00&lt;?, ?it...
# ask-marvin
p
@Marvin 0%| | 0/100 [00:00<?, ?it/s]141829.570 | ERROR | prefect.flow_runs.runner - Process for flow run 'unnatural-shrimp' exited with status code: -7 141829.606 | INFO | prefect.flow_runs.runner - Reported flow run 'ae24c72d-e40d-41d7-a62b-2415ee23bdc5' as crashed: Flow run process exited with non-zero status code -7. 141829.643 | INFO | Flow run 'unnatural-shrimp' - Downloading flow code from storage at '.' ^C141852.861 | INFO | prefect.runner - Pausing schedules for all deployments... 141852.876 | INFO | prefect.runner - All deployment schedules have been paused! Number CUDA Devices: 4
m
It appears the error you encountered,
Flow run process exited with non-zero status code -7
, doesn't have an exact match in the Prefect GitHub issues, but there's a similar problem where flows are flagged as crashed when they actually are not (https://github.com/PrefectHQ/prefect/issues/10991). This may not be an exact solution to your problem but provides an insight into potential misclassification of flow run statuses in Prefect; unfortunately, no direct solution is present for your specific error code. A useful step could be ensuring you have the latest Prefect version installed and checking for updates, bug fixes, or related issues in newer releases. Issues not identical but potentially related include: - Problems with flow status reporting: https://github.com/PrefectHQ/prefect/issues/10991 - Issues with asynchronous context managers: https://github.com/PrefectHQ/prefect/issues/9412 - Problems with agent CLI flags: https://github.com/PrefectHQ/prefect/issues/8123 Would you like to check for the latest Prefect version to see if an upgrade might contain a fix for your issue?