I m getting a weird error even though my flow exists ```pref

Question

I m getting a weird error even though my flow exists ```prefect exceptions MissingFlowError Flow tool not found in script flows tool py Found the following flows monolithic tool flow Check to make sure that your flow function is decorated with ` flow` ``` I have the flow defined as ```flows tool py flow name= monolithic tool flow def process tool ``` and deploy like ```prefect deployment build flows tool py process tool n process tool q test ib docker container local override image=sha256 4e3346168cs3a3c6c0fb256d6e705c6629a41f0f6f23405c33a0bbc3deb964690 apply```

Aaron Goebel · Answer

Deployment works Running does not

Aaron Goebel · Answer

I m packaging my flow with docker This was working yesterday

Aaron Goebel · Answer

Weirdly renaming the flow worked

Mike Grabbe · Answer

I think this might be related to the 2 7 2 release I just updated my images and I m getting these errors as well

Mike Grabbe · Answer

```prefect exceptions MissingFlowError Flow opsjira extract flow not found in script flows opsjira extract flow py Found the following flows dbt cli command opsjira extract flow Check to make sure that your flow function is decorated with ` flow` ```

Mike Grabbe · Answer

I m guessing it has to do with the changes introduced in this PR <https github com PrefectHQ prefect pull 7817> I reverted back to 2 7 1 on my flow run images and things are back to normal

Rajeshwar Agrawal · Answer

I am seeing the same issue with 2 7 2

Rajeshwar Agrawal · Answer

its seems that flow name with underscore in the function name do not work as deployment build command tries to find the flow with dashed case instead of underscores

Rajeshwar Agrawal · Answer

`my flow` throws an error saying throws an error ```Flow my flow not found in script flow flow py Found the following flows my flow Check to make sure that your flow function is decorated with ` flow` ```

Rajeshwar Agrawal · Answer

but `myflow` worked

Anna Geller · Answer

thanks everyone for reporting I was able to reproduce and opened a ticket we ll fix that asap <https github com PrefectHQ prefect issues 7918>

Anna Geller · Answer

ofc it had to be the line 42 that causes the issue 42

Anna Geller · Answer

Peyton fixed it here <https github com PrefectHQ prefect pull 7920 files>

Peyton Runyan · Answer

Thanks for the help yall <https prefect community slack com archives C01TK7XSLT0 p1671201324084329>