Any idea what could be causing a flow to fail with the error "Parameter object has no attribute 'task_run_name'" when using Docker storage? The docker image build was fine and passed its health checks, and the flow runs fine when using local storage (and local agent) instead. Note this happens only if I use a custom Dockerfile.

@Bruce Haggerty We had encountered this once when the local prefect version we used to register the flow didn’t match the prefect version of our execution environment

Amazing! Thank you, that fixed it! Very much appreciate the help!!

Nice - Glad to be of help !

@josh is there a better way to enforce this and provide clearer error messages?