From 68c7cda42ec015fa222e4d377b343cadce360e08 Mon Sep 17 00:00:00 2001 From: Ana <84312885+AnaLoznianu@users.noreply.github.com> Date: Wed, 25 Oct 2023 18:22:02 +0300 Subject: [PATCH] Update developers/compute-to-data/compute-workflow.md Co-authored-by: Bogdan Fazakas --- developers/compute-to-data/compute-workflow.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/developers/compute-to-data/compute-workflow.md b/developers/compute-to-data/compute-workflow.md index ab5861ac..427f4135 100644 --- a/developers/compute-to-data/compute-workflow.md +++ b/developers/compute-to-data/compute-workflow.md @@ -15,7 +15,7 @@ Below, we'll outline each step in detail 📝 ## Starting a C2D Job 1. The consumer initiates a compute-to-data job by selecting the desired data asset and algorithm. 2. The provider checks the orders on the blockchain. -3. If the orders are valid, the provider can commence the compute flow. +3. If the orders for data asset, algorithm and compute environment fees are valid, the provider can commence the compute flow. 4. The provider informs the consumer of the job number's successful creation. 5. With the job ID and confirmation of the orders, the consumer starts the job by calling the operator service. 6. The operator service communicates with the operator engine to initiate a new job.