# Inefficient workflow design in AWS Step Functions Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-workflow-design-in-aws-step-functions Improper design choices in AWS Step Functions can lead to unnecessary charges. By: Jarred Clore Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Inefficient Workflow Design in AWS Step Functions The short version Improper design choices in AWS Step Functions can lead to unnecessary charges. [Jarred Clore](https://www.linkedin.com/in/jarred-clore/) Cloud FinOps Delivery Leader @ Cisco AWS service [AWS Step Functions](https://www.pointfive.co/efficiency-hub/cloud-services/aws-step-functions) Category [Compute](https://www.pointfive.co/efficiency-hub/service-category/compute) Reference CER-0176 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. For example: - Using Standard Workflows for short-lived, high-frequency executions leads to excessive per-transition charges. - Using Express Workflows for long-running processes (close to or exceeding the 5-minute limit) may cause timeouts or retries. - Inefficient use of states - such as chaining many simple states instead of combining logic into a Lambda function-can increase cost in both workflow types. - Overuse of payload-passing between states (especially in Express workflows) increases billed memory and therefore the GB-second duration charge. ## Billing model The pricing dimensions that drive this cost. - Standard Workflows: Billed per state transition - Express Workflows: Billed per request and by duration, with billed memory (in 64-MB increments) driven by the workflow definition size, Map or Parallel state use, and payload size - Choosing the wrong workflow type or poorly structuring a workflow (e.g., excessive state transitions) can significantly inflate costs, especially under high execution volumes or when parallel states and payload sizes are not optimized. ## How to detect 6 checks to find it in your estate. - Express workflows frequently hit duration or payload limits - Short-lived workflows are using Standard instead of Express - The number of state transitions is unusually high relative to the business logic - Simple sequential logic could be collapsed into a Lambda or intrinsic function - Map and Parallel states are overused or not optimized - Input/output payload sizes between states are larger than necessary ## How to fix 6 ways to remove the waste. - Choose Express workflows for short-lived, high-volume executions - Use Standard workflows for long-running, infrequent executions - Combine simple logic steps into a single Lambda or use intrinsic functions - Use ResultPath , OutputPath , and Parameters fields efficiently to trim payloads - Minimize use of unnecessary Map or Parallel states where linear processing suffices - Benchmark costs and execution patterns using AWS Step Functions metrics ## Documentation Vendor references for pricing and configuration. - [Choosing workflow type in Step Functions docs.aws.amazon.com](https://docs.aws.amazon.com/step-functions/latest/dg/choosing-workflow-type.html) - [AWS Step Functions Pricing aws.amazon.com](https://aws.amazon.com/step-functions/pricing/) - [Best practices for Step Functions docs.aws.amazon.com](https://docs.aws.amazon.com/step-functions/latest/dg/sfn-best-practices.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS EC2 CER-0327 ### [Spot Instance Overreliance Without Effective Cost-Per-Performance Analysis](https://www.pointfive.co/efficiency-hub/inefficiencies/spot-instance-overreliance-without-cost-per-performance-analysis) Organizations frequently pursue aggressive Spot Instance adoption based on headline discount percentages - up to 90% off On-Demand pricing - without evaluating the effective cost per unit of work completed. While Spot pricing can deliver... Compute - AWS Lambda CER-0204 ### [Inefficient SnapStart Configuration in Lambda](https://www.pointfive.co/efficiency-hub/inefficiencies/inefficient-snapstart-configuration-in-lambda) SnapStart reduces cold-start latency, but when configured inefficiently, it can increase costs. For Python and .NET functions, high-traffic workloads can trigger frequent snapshot restorations, multiplying costs. Slow initialization code... Compute - AWS Lambda CER-0230 ### [Excessive Lambda Duration from Synchronous Waiting](https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-lambda-duration-from-synchronous-waiting) Some Lambda functions perform synchronous calls to other services, APIs, or internal microservices and wait for the response before proceeding. During this time, the Lambda is idle from a compute perspective but still fully billed. This... Compute --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.