@Marvin I am using Prefect 2.19.3 and am using serverless push workers in Azure. This morning all my flow runs have been crashed, I looked into the containers and they fail from : AttributeError: 'Flow' object has no attribute 'should_validate_parameters'. Did you mean: 'validate_parameters'? I have not changed my code yesterday in any of the flows that ran, how can I fix this? what is causing the issue. I found an article saying the use of

from __future__ import annotations

causes this, but I do not have it in my code.

It seems like your flows encountering the

'Flow' object has no attribute 'should_validate_parameters'

error is likely related to an internal change or mismatch in Prefect's code that your deployments may not be aligned with. Here’s what might help you resolve this: 1. Environment Consistency: The troubleshooting guide advising that your flow and worker/agent versions should be consistent. It's possible that even a minor difference between versions can cause unexpected errors. Make sure both your flow environments and the Prefect workers are using the exact same version. 2. Logs: Reviewing detailed logs might give further insight into what is being called and causing the error. This guide also recommends checking logs at different levels, specifically increasing the level to

DEBUG

to capture more information might be helpful. 3. Type Hints and Parameter Validation: There are sections in the Prefect 2.x documentation speaking about how Prefect uses parameter schema validation with type hints. Ensure that there have been no updates in the way

validate_parameters

is used or defined versus

should_validate_parameters

. Any discrepancies should be handled by checking documentation or updating your code to align with the library's requirements. You mentioned not using the

from __future__ import annotations

, which often causes similar errors, so that's ruled out. Here’s the GitHub issue discussing that specific PIT fall. If none of the above fixes work, it might be worth checking if the issue persists with a slightly newer or even slightly older version of Prefect, as sometimes regressions or breaking changes can occur in minor versions. Good luck, and remember to stay optimistic, even though the flow isn't quite flowing right now!