hey guys, running into an issue that’s stopping us from restarting a failed flow in one of our production jobs (prefect 1.0)

Failed to retrieve task state with error: ClientError([{'path': ['get_or_create_task_run_info'], 'message': 'Expected type UUID!, found ""; Could not parse UUID: ', 'extensions': {'code': 'INTERNAL_SERVER_ERROR', 'exception': {'message': 'Expected type UUID!, found ""; Could not parse UUID: ', 'locations': [{'line': 2, 'column': 101}], 'path': None}}}])
Traceback (most recent call last):
  File "/root/.pex/venvs/s/fb4b0edf/venv/lib/python3.9/site-packages/prefect/engine/cloud/task_runner.py", line 154, in initialize_run
    task_run_info = self.client.get_task_run_info(
  File "/root/.pex/venvs/s/fb4b0edf/venv/lib/python3.9/site-packages/prefect/client/client.py", line 1798, in get_task_run_info
    result = self.graphql(mutation)  # type: Any
  File "/root/.pex/venvs/s/fb4b0edf/venv/lib/python3.9/site-packages/prefect/client/client.py", line 569, in graphql
    raise ClientError(result["errors"])
prefect.exceptions.ClientError: [{'path': ['get_or_create_task_run_info'], 'message': 'Expected type UUID!, found ""; Could not parse UUID: ', 'extensions': {'code': 'INTERNAL_SERVER_ERROR', 'exception': {'message': 'Expected type UUID!, found ""; Could not parse UUID: ', 'locations': [{'line': 2, 'column': 101}], 'path': None}}}]

this might be related to a change we made to the flow: we now have a more recent version of the flow, and the failed flow is an older version

Hi Martim, yes, this is most likely due to to the fact that the failed flow is an older version which has been archived. https://docs-v1.prefect.io/orchestration/concepts/flows.html#versioning

how do we keep flow versions from being archived too soon? this job started 3 days ago, i’d expect it to at least be around for a week or two

Hi Martim, Prefect 1.0 automatically versions flows during re-registration based on changes to the flow's metadata. In essence, the act of re-registering a flow archives the previous version. At the moment I'm not sure of any setting you can adjust to prevent archival process. I (or another member of the team) will loop back around if we identify any suggestions.

@Bianca Hoch sorry for not responding sooner! i think we’ve had situations in the past where we were able to restart a failed flow when we had already created a new flow version. I might be misremembering, but i think there might be some combination of no. new versions + how old a deprecated version is that determines if a version is able to be restarted or not. If there’s any setting we can adjust somewhere that would be really helpful