Step Functions for workflows in AWS - Step-by-Step Execution

Process Flow - Step Functions for workflows

Start Execution

↓

State 1: Task or Choice

↓

State 2: Task or Choice

↓

State 3: Task or Choice

↓

Success or Failure

↓

End Execution

Step Functions run a series of steps (states) in order, moving from one task or decision to the next until the workflow finishes.

Execution Sample

AWS

{
  "StartAt": "Step1",
  "States": {
    "Step1": {"Type": "Task", "Next": "Step2"},
    "Step2": {"Type": "Task", "End": true}
  }
}

This workflow runs Step1, then Step2, then ends successfully.

Process Table

Step	Current State	Action	Next State	Status
1	Step1	Execute Task	Step2	Running
2	Step2	Execute Task	None	Success
3	End	Workflow ends	None	Completed

💡 Workflow ends after Step2 completes successfully.

Status Tracker

Variable	Start	After Step1	After Step2	Final
ExecutionStatus	NotStarted	Running	Running	Succeeded
CurrentState	None	Step1	Step2	End

Key Moments - 2 Insights

Why does the workflow move from Step1 to Step2 automatically?

Because Step1's definition has "Next": "Step2", so after Step1 finishes, Step2 starts automatically (see execution_table step 1).

What happens if a state has "End": true?

The workflow stops after that state completes successfully, as shown in Step2 with "End": true (execution_table step 2).

Visual Quiz - 3 Questions

Look at the execution_table, what is the Current State at Step 2?

A Step1

B End

C Step2

D None

💡 Hint

Check the 'Current State' column in execution_table row for Step 2.

At which step does the workflow end?

A Step 2

B Step 3

C Step 1

D It never ends

💡 Hint

Look at the 'Status' column and see when it says 'Completed' in execution_table.

If Step1 had no "Next" or "End" field, what would happen?

A Workflow would fail or stop at Step1

B Workflow would skip Step1

C Workflow would continue to Step2 automatically

D Workflow would loop back to Step1

💡 Hint

Step1 must specify where to go next or end, otherwise workflow cannot continue (see key_moments).

Concept Snapshot

Step Functions define workflows as states.
Each state runs a task or makes a choice.
Use "Next" to go to the next state.
Use "End": true to finish the workflow.
States run in order until success or failure.

Full Transcript

AWS Step Functions let you build workflows by defining states. Each state can be a task or a decision point. The workflow starts at the state named in StartAt. After a state finishes, it moves to the next state defined by the "Next" field. If a state has "End": true, the workflow stops after that state. This way, you can chain tasks step-by-step to automate processes. The execution table shows each step running in order until the workflow completes successfully.

Practice

1. What is the main purpose of AWS Step Functions in a workflow?

easy

A. To monitor network traffic between AWS services

B. To coordinate and manage the sequence of tasks in a workflow

C. To provide a user interface for AWS services

D. To store large amounts of data for applications

Solution

1. Step 1: Understand the role of Step Functions

   AWS Step Functions help organize and control the order of tasks in a workflow, making sure each step runs in sequence or parallel as needed.

2. Step 2: Compare with other AWS services

   Other options describe storage, UI, or monitoring, which are not the main functions of Step Functions.

3. Final Answer:

   To coordinate and manage the sequence of tasks in a workflow -> Option B

4. Quick Check:

   Step Functions = task coordination [OK]

Hint: Step Functions organize tasks step-by-step [OK]

Common Mistakes:

• Confusing Step Functions with storage services
• Thinking Step Functions provide UI
• Assuming Step Functions monitor network traffic

2. Which JSON field is required to define a task state in an AWS Step Functions state machine?

easy

A. "Timeout" specifying the maximum execution time

B. "Retry" specifying the retry policy

C. "InputPath" specifying the input data format

D. "Resource" specifying the ARN of the task to run

Solution

1. Step 1: Identify the key field for task execution

   The "Resource" field is mandatory in a task state to specify which AWS service or Lambda function to invoke.

2. Step 2: Understand other fields

   "Timeout", "InputPath", and "Retry" are optional fields that control behavior but are not required to define a task.

3. Final Answer:

   "Resource" specifying the ARN of the task to run -> Option D

4. Quick Check:

   Task state needs "Resource" [OK]

Hint: "Resource" points to the task to run [OK]

Common Mistakes:

• Confusing optional fields with required ones
• Using "Timeout" as a required field
• Forgetting to specify the task ARN

3. Given this Step Functions snippet, what is the next state after TaskA completes successfully?

{
  "StartAt": "TaskA",
  "States": {
    "TaskA": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:123456789012:function:FunctionA",
      "Next": "TaskB"
    },
    "TaskB": {
      "Type": "Task",
      "Resource": "arn:aws:lambda:region:123456789012:function:FunctionB",
      "End": true
    }
  }
}

medium

A. TaskB

B. TaskA

C. End state

D. No next state defined

Solution

1. Step 1: Read the "Next" field of TaskA

   The JSON shows "Next": "TaskB" for TaskA, meaning after TaskA finishes, the workflow moves to TaskB.

2. Step 2: Confirm TaskB is defined

   TaskB is defined and marked with "End": true, so it is the final step after TaskA.

3. Final Answer:

   TaskB -> Option A

4. Quick Check:

   TaskA's "Next" = TaskB [OK]

Hint: Check the "Next" field for the following state [OK]

Common Mistakes:

• Assuming TaskA loops to itself
• Thinking workflow ends after TaskA
• Ignoring the "Next" field

4. You have this Step Functions state definition:

{
  "Type": "Task",
  "Resource": "arn:aws:lambda:region:123456789012:function:MyFunction",
  "Next": "NextState"
}

What is missing that could cause a failure if the Lambda function errors?

medium

A. "Catch" block to handle errors

B. "TimeoutSeconds" field to limit execution time

C. "ResultPath" to store output

D. "StartAt" field to define the first state

Solution

1. Step 1: Identify error handling in Step Functions

   Without a "Catch" block, errors from the Lambda function cause the workflow to fail immediately.

2. Step 2: Understand other fields

   "TimeoutSeconds" limits time but is optional; "ResultPath" controls output storage; "StartAt" is for the state machine root, not individual states.

3. Final Answer:

   "Catch" block to handle errors -> Option A

4. Quick Check:

   Error handling needs "Catch" [OK]

Hint: Add "Catch" to handle task errors safely [OK]

Common Mistakes:

• Confusing "TimeoutSeconds" with error handling
• Omitting "Catch" causes workflow failure on error
• Thinking "StartAt" is needed inside a task

5. You want to build a workflow that runs two Lambda functions in parallel and then proceeds only when both finish successfully. Which Step Functions state type should you use?

hard

A. Map state

B. Choice state

C. Parallel state

D. Pass state

Solution

1. Step 1: Understand the requirement for parallel execution

   Running two Lambda functions at the same time and waiting for both to finish requires a "Parallel" state.

2. Step 2: Review other state types

   "Choice" is for branching decisions, "Map" is for iterating over items, and "Pass" passes data without work.

3. Final Answer:

   Parallel state -> Option C

4. Quick Check:

   Parallel state runs tasks simultaneously [OK]

Hint: Use Parallel state to run tasks together [OK]

Common Mistakes:

• Using Choice state for parallelism
• Confusing Map state with parallel execution
• Thinking Pass state runs tasks