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

*EDIT:* _This was because my dask runners were not accessing the same orion database._ 

Hey! I was testing to run orion with a DaskCluster that is deployed in kubernetes;

I’m starting the flow locally and point to the daskcluster on localhost - (using port-forwarding for the scheduler)
When running a local DaskCluster it works fine

I’m always getting this error:

```distributed.worker - WARNING - Compute Failed
Function:  orchestrate_task_run
args:      ()
kwargs:    {'task': &lt;prefect.tasks.Task object at 0x7f02f0f56430&gt;, 'task_run': TaskRun(id=UUID('2acf899f-67f5-4717-9665-c91f730f3719'), created=datetime.datetime(2022, 1, 16, 11, 45, 38, 995585, tzinfo=datetime.timezone.utc), updated=datetime.datetime(2022, 1, 16, 11, 45, 39, 19000, tzinfo=datetime.timezone.utc), name='get-product-b7ee3036-0', flow_run_id=UUID('a3e75090-2e7d-42f6-8dda-b00600f70b12'), task_key='b7ee3036fbe1354fe2fbf30215a316c4', dynamic_key='0', cache_key=None, cache_expiration=None, task_version=None, empirical_policy=TaskRunPolicy(max_retries=10, retry_delay_seconds=0.0), tags=[], state_id=UUID('36aa692f-175d-4bff-81ed-e57f2228cdfa'), task_inputs={}, state_type=StateType.PENDING, run_count=0, expected_start_time=datetime.datetime(2022, 1, 16, 11, 45, 38, 988955, tzinfo=datetime.timezone.utc), next_scheduled_start_time=None, start_time=None, end_time=None, total_run_time=datetime.timedelta(0), estimated_run_time=datetime.timedelta(0), estimated_start_time_delta=datetime.timedelta
Exception: "ValueError('Invalid task run: 2acf899f-67f5-4717-9665-c91f730f3719')"```
Is there something obvious I’m missing?

Do my dask-workers need to be able to access the orion db?

Does the EDIT mean that you found a solution? LMK if this is still an open issue.

But to still answer your question: I’m not 100% sure but I think the relationship is reverse: the Orion engine needs to be able to access Dask to check on the execution state for orchestration and bookkeeping of task run states.

Hey <@U02H1A95XDW>. Yes I got it to run. If I understand it correctly it needs both though. Once the task is triggered in dask it checks for it’s id in the database right?