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.

Prefect Community

We are trying to figure out how a flow running in Prefect Cloud might fail with
```Failed to find current tenant None in result  {'data': {'tenant': [{'id': 'foo-400d-4288-8020-...', 'slug': '&lt;redacted&gt;'}]}}```
when it attempts to trigger another flow run via `StartFlowRun` .

The "sub"-flow succeeds when running by itself and was registered the same way as the flow that attempts to start it.

Hi <@UNEEY59Q9>, that is weird. What Prefect version are you on?

Can you show me the output of `prefect diagnostics` ?

I think this may have been fixed in 0.15.1. <https://docs.prefect.io/api/latest/changelog.html#_0-15-1|changelog here>

Related <https://github.com/PrefectHQ/prefect/pull/4758|PR> . Maybe you can move to using `--key` as opposed to the deprecated `--token`?

It looks like using 0.15.1 instead of 0.15.0 resolved this. Thanks!!