, then it’s running only locally and the flow run is not stored in the backend. But if you use
prefect run --id flow-uuid
, then you trigger a flow run via API and you can inspect the results in the Prefect Cloud UI or API. So the latter is equivalent to a quick run in the UI.
c
Chris Arderne
11/16/2021, 11:51 AM
Thanks @Anna Geller. The purpose of running it locally it is to test runs more quickly by skipping VertexRun and associated infrastructure. But will just remove that task from reference tasks and ignore failure, as it's only needed when running on Cloud.
a
Anna Geller
11/16/2021, 11:55 AM
Got it. Yeah, with serverless it always take some time to spin up resources, so I can totally understand that running locally is much easier to test things out.
k
Kevin Kho
11/16/2021, 2:59 PM
Does local here mean
flow.run()
or local agent? There is a flag for cloud triggered runs
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.