Bring your towel and join one of the fastest growing data communities. Welcome to our second-generation open source orchestration platform, a completely rethought approach to dataflow automation.

Prefect Community

Hi guys,
I am having an issue with one of my flows not terminating due to a single mapped task ("mapped child 1") being stuck in `pending` indefinitely. Not even the timeout provided to `@task` gets triggered.
When checking the logs for the mapped task in question, I found what seems to be an internal server error (see thread).
Rerunning it multiple times in the past resulted in the same issue (with the same exception), except this Saturday when it miraculously succeeded but then failed again the next day.

Is that exception the cause of the problem? Is the issue on prefect's side or on mine? Thanks in advance

Exception:
```Failed to retrieve task state with error: ClientError([{'path': ['get_or_create_task_run'], 'message': 'Invalid ID', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}])
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/site-packages/prefect/engine/cloud/task_runner.py", line 190, in initialize_run
    task_run_info = self.client.get_task_run_info(
  File "/usr/local/lib/python3.8/site-packages/prefect/client/client.py", line 1227, in get_task_run_info
    result = self.graphql(mutation)  # type: Any
  File "/usr/local/lib/python3.8/site-packages/prefect/client/client.py", line 294, in graphql
    raise ClientError(result["errors"])
prefect.utilities.exceptions.ClientError: [{'path': ['get_or_create_task_run'], 'message': 'Invalid ID', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]```

Hey <@U0191FPCKS6>,
I believe this issue was caused by a rare race condition that was resolved early this morning. For your issue described here, I recommend upgrading your Flow to 0.13.18 (being released later today) for best results.