Getting this error with the fivetran syncs when I move `awai

Question

Getting this error with the fivetran syncs when I move `await` from the function any ideas ```A sync compatible method was called from a context that was previously async but is now sync The sync call must be changed to run in a worker thread to support sending the coroutine for load to the main thread ```

Madison Schott · Answer

``` task def webevent sync fivetran credentials webevents secret = Secret load webevents connector id webevents sync = trigger fivetran connector sync and wait for completion fivetran credentials=fivetran credentials connector id=webevents secret get schedule type= manual poll status every n seconds=30 ```

Madison Schott · Answer

I got rid of the `await` in front of the class name

Madison Schott · Answer

I want to call the sync from a flow and have the sync run when the flow does

Nate · Answer

It looks like you re calling the trigger fivetran connector flow from within a task where calling flows tasks from tasks is not supported can you try making your webevent sync task a flow

Madison Schott · Answer

Ah that is a flow The documentation doesn t make that super clear

Madison Schott · Answer

So a flow can be called within a flow

Madison Schott · Answer

``` flow def winc sync fivetran credentials winc secret = Secret load winc connector id winc sync = trigger fivetran connector sync and wait for completion fivetran credentials=fivetran credentials connector id=winc secret get schedule type= manual poll status every n seconds=30 ```

Madison Schott · Answer

Is this way of calling it within the other flow correct ``` flow def data pipeline 2 run data syncs with Fivetran print Pipeline 2 0 is working fivetran credentials = FivetranCredentials api key= my api key api secret= my api secret sync <http Winc com|Winc com> data winc sync = winc sync fivetran credentials ```

Nate · Answer

gt Ah that is a flow The documentation doesn t make that super clear yep we can reach out to the maintainers at fivetran and propose some updates to the docs gt So a flow can be called within a flow yep this was a big motivator for prefect 2 allowing flows to be called directly from other flows and yes that looks right

Madison Schott · Answer

Great thanks So this is what fixed that issue of not using `await` I m still confused as to what that does and how it s different with or without

Nate · Answer

I m still looking into the exact reason you got that message bc I would have expected an error like this in your case ```RuntimeError Flows cannot be run from within tasks Did you mean to call this flow in a flow ``` but in general I think its safe to say if your main flow decorated function is defined as a sync function not `async def` just `def` then you should treat everything inside as a callable a normal function you don t have to `await` because prefect knows how handle things like `Secret load` in a sync context if your main flow is async you will have to await flows tasks functions that are defined as asynchronous functions