How to: Author and manage workflows

Note

Dapr Workflow is currently in beta. See known limitations for 1.14.1.

Let’s create a Dapr workflow and invoke it using the console. With the provided workflow example, you will:

This example uses the default configuration from dapr init in self-hosted mode.

Prerequisites

Set up the environment

Clone the JavaScript SDK repo and navigate into it.

  1. git clone https://github.com/dapr/js-sdk
  2. cd js-sdk

From the JavaScript SDK root directory, navigate to the Dapr Workflow example.

  1. cd examples/workflow/authoring

Run the following command to install the requirements for running this workflow sample with the Dapr JavaScript SDK.

  1. npm install

Run the activity-sequence.ts

The activity-sequence file registers a workflow and an activity with the Dapr Workflow runtime. The workflow is a sequence of activities that are executed in order. We use DaprWorkflowClient to schedule a new workflow instance and wait for it to complete.

  1. const daprHost = "localhost";
  2. const daprPort = "50001";
  3. const workflowClient = new DaprWorkflowClient({
  4.   daprHost,
  5.   daprPort,
  6. });
  7. const workflowRuntime = new WorkflowRuntime({
  8.   daprHost,
  9.   daprPort,
  10. });
  12. const hello = async (_: WorkflowActivityContext, name: string) => {
  13.   return `Hello ${name}!`;
  14. };
  16. const sequence: TWorkflow = async function* (ctx: WorkflowContext): any {
  17.   const cities: string[] = [];
  19.   const result1 = yield ctx.callActivity(hello, "Tokyo");
  20.   cities.push(result1);
  21.   const result2 = yield ctx.callActivity(hello, "Seattle");
  22.   cities.push(result2);
  23.   const result3 = yield ctx.callActivity(hello, "London");
  24.   cities.push(result3);
  26.   return cities;
  27. };
  29. workflowRuntime.registerWorkflow(sequence).registerActivity(hello);
  31. // Wrap the worker startup in a try-catch block to handle any errors during startup
  32. try {
  33.   await workflowRuntime.start();
  34.   console.log("Workflow runtime started successfully");
  35. } catch (error) {
  36.   console.error("Error starting workflow runtime:", error);
  37. }
  39. // Schedule a new orchestration
  40. try {
  41.   const id = await workflowClient.scheduleNewWorkflow(sequence);
  42.   console.log(`Orchestration scheduled with ID: ${id}`);
  44.   // Wait for orchestration completion
  45.   const state = await workflowClient.waitForWorkflowCompletion(id, undefined, 30);
  47.   console.log(`Orchestration completed! Result: ${state?.serializedOutput}`);
  48. } catch (error) {
  49.   console.error("Error scheduling or waiting for orchestration:", error);
  50. }

In the code above:

  • workflowRuntime.registerWorkflow(sequence) registers sequence as a workflow in the Dapr Workflow runtime.
  • await workflowRuntime.start(); builds and starts the engine within the Dapr Workflow runtime.
  • await workflowClient.scheduleNewWorkflow(sequence) schedules a new workflow instance with the Dapr Workflow runtime.
  • await workflowClient.waitForWorkflowCompletion(id, undefined, 30) waits for the workflow instance to complete.

In the terminal, execute the following command to kick off the activity-sequence.ts:

  1. npm run start:dapr:activity-sequence

Expected output

  1. You're up and running! Both Dapr and your app logs will appear here.
  3. ...
  5. == APP == Orchestration scheduled with ID: dc040bea-6436-4051-9166-c9294f9d2201
  6. == APP == Waiting 30 seconds for instance dc040bea-6436-4051-9166-c9294f9d2201 to complete...
  7. == APP == Received "Orchestrator Request" work item with instance id 'dc040bea-6436-4051-9166-c9294f9d2201'
  8. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Rebuilding local state with 0 history event...
  9. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Processing 2 new history event(s): [ORCHESTRATORSTARTED=1, EXECUTIONSTARTED=1]
  10. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Waiting for 1 task(s) and 0 event(s) to complete...
  11. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Returning 1 action(s)
  12. == APP == Received "Activity Request" work item
  13. == APP == Activity hello completed with output "Hello Tokyo!" (14 chars)
  14. == APP == Received "Orchestrator Request" work item with instance id 'dc040bea-6436-4051-9166-c9294f9d2201'
  15. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Rebuilding local state with 3 history event...
  16. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Processing 2 new history event(s): [ORCHESTRATORSTARTED=1, TASKCOMPLETED=1]
  17. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Waiting for 1 task(s) and 0 event(s) to complete...
  18. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Returning 1 action(s)
  19. == APP == Received "Activity Request" work item
  20. == APP == Activity hello completed with output "Hello Seattle!" (16 chars)
  21. == APP == Received "Orchestrator Request" work item with instance id 'dc040bea-6436-4051-9166-c9294f9d2201'
  22. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Rebuilding local state with 6 history event...
  23. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Processing 2 new history event(s): [ORCHESTRATORSTARTED=1, TASKCOMPLETED=1]
  24. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Waiting for 1 task(s) and 0 event(s) to complete...
  25. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Returning 1 action(s)
  26. == APP == Received "Activity Request" work item
  27. == APP == Activity hello completed with output "Hello London!" (15 chars)
  28. == APP == Received "Orchestrator Request" work item with instance id 'dc040bea-6436-4051-9166-c9294f9d2201'
  29. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Rebuilding local state with 9 history event...
  30. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Processing 2 new history event(s): [ORCHESTRATORSTARTED=1, TASKCOMPLETED=1]
  31. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Orchestration completed with status COMPLETED
  32. == APP == dc040bea-6436-4051-9166-c9294f9d2201: Returning 1 action(s)
  33. INFO[0006] dc040bea-6436-4051-9166-c9294f9d2201: 'sequence' completed with a COMPLETED status.  app_id=activity-sequence-workflow instance=kaibocai-devbox scope=wfengine.backend type=log ver=1.12.3
  34. == APP == Instance dc040bea-6436-4051-9166-c9294f9d2201 completed
  35. == APP == Orchestration completed! Result: ["Hello Tokyo!","Hello Seattle!","Hello London!"]

Next steps