this appears to work, however this workflow does not get triggered if I test via the web GUI for example.

prefect register flow --file $MODULE_LOC/the_flow/flow.py --project the_proj
Warning: `prefect register flow` is deprecated, please transition to using `prefect register` instead.
Flow URL: <http://localhost:8080/default/flow/eb320e0d-18ab-426f-9929-1b880cf1fadb>
 └── ID: 4e9d85e9-39a0-4e72-a6fb-55941c12bac7
 └── Project: the_proj
 └── Labels: ['ip-172-20-3-23.ec2.internal']

(this works)

prefect register --project the_proj -p the_flow/
Collecting flows...
Processing 'the_flow/flow.py':
  Building `Local` storage...
  Registering 'Flow_name'... Done
  └── ID: f9cfe0ca-848d-44b5-a739-566a5c77b387
  └── Version: 5

this doesn't, although it gives the impression it has.

The

prefect register --project the_proj -p the_flow/

worked for me. What Prefect version are you on?

How many flows do you have in that folder?

Just to be clear, the registration appears to work. The flow is created, gets an ID, is listed, and appears to be available to use. If I invoke it however it does not get triggered and eventually times out. If I use the old syntax there's no issue.

@Marvin open “Relative Path in prefect register CLI Not Being Converted to Absolute”