Hey folks -- I had a question. I haven't tried this, but in looking at the API docs, it looks like it's possible to trigger a flow run with parameters without having to have that wrapped up in a Deployment. Under what conditions would it make sense to just trigger an adhoc flow run like this vs. having a full deployment? (For context, this is with locally-hosted Orion server/UI.) Currently we are using the API to create a flow run from a deployment.

You can create a flow run without having a deployment, that’s the route that we call when a flow is called interactively (i.e. not managed by an agent).

Ah! Ok, that's helpful. So "no deployment" = "no agent running this" -- (it just runs on the server?)

“no deployment” == “reporting that a flow is running” rather than “scheduling a run for execution”

Sorry, I'm not sure I'm fully understanding this distinction 🙂 If triggering a flow run (without Deployment) via API, where would that flow run?

you aren’t triggering it, you are merely telling the API it exists

💡💡💡 Ahhh! Ok -- that really clarifies it, thank you! So it sounds like this really wouldn't be an API path you'd expect to be used externally.

You could use it to track a flow run you were manually orchestrating, but otherwise yeah I wouldn’t expect a user to call it 🙂

Ok, thanks again for your patience in clarifying this.