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

anyone seen this kind of error message before: `prefect.exceptions.ClientError: [{'path': ['set_task_run_states'], 'message': 'State update failed for task run ID d253a979-2ad4-4add-9c60-e569d75758e6: provided a running state but associated flow run 165e6a96-0e0d-464b-9a85-fc97454b9375 is not in a running state.', 'extensions': {'code': 'INTERNAL_SERVER_ERROR'}}]`
I have a flow that kicks off a few hundred flow runs, and it was working fine in a test environment, but I got this as soon as I tried to run it in a production environment

This seems like something was marked as failed or a terminal state, and then the flow process continued to run. When it tries to update state, it will hit this. Did some of the flow runs fail to start?

If they did fail to start those error messages were covered up by these ones. But I will look into that tomorrow, that seems likeliest

Actually, i'm sure that is it. The production environment has required parameters without defaults. If i see it again I'll check if there are other messages about the flows failing to start, because that would have helped me out