---
title: >-
  Shopify Flow: Changes to Action extensions result in fewer breaking changes -
  Shopify developer changelog
description: >-
  Shopify’s developer changelog documents all changes to Shopify’s platform.
  Find the latest news and learn about new platform opportunities.
source_url:
  html: >-
    https://shopify.dev/changelog/shopify-flow-changes-to-action-extensions-result-in-fewer-breaking-changes
  md: >-
    https://shopify.dev/changelog/shopify-flow-changes-to-action-extensions-result-in-fewer-breaking-changes.md
metadata:
  effectiveApiVersion: 2026-07
  affectedApi: []
  primaryTag:
    displayName: Tools
    handle: tools
  secondaryTag:
    displayName: Update
    handle: update
  indicatesActionRequired: false
  createdAt: '2026-06-26T14:57:16-04:00'
  postedAt: '2026-07-07T12:00:00-04:00'
  updatedAt: '2026-07-07T16:02:19-04:00'
  effectiveAt: '2026-07-08T12:00:00-04:00'
---

July 7, 2026

Tags:

* Tools
* 2026-07

# Shopify Flow: Changes to Action extensions result in fewer breaking changes

Your server-side code now has more control over how breaking changes to an action’s configuration fields are handled. Instead of failing validation when there’s a field mismatch, workflows that use older versions of an action will continue to execute, and Shopify will still send the request to the configured endpoint URL. Your server can then decide how to handle schema differences: for example, it can set default values for new required fields, ignore fields that were removed, or reject the request.

## Why it’s changing

Previously, any change to an action’s configuration fields was treated as a breaking change in merchant workflows. Runtime validation would fail, and Shopify wouldn’t send the request to the partner server. For example, if a new required field was added or an existing field was removed, any workflows using an older version of that action would always fail and never reach your endpoint.

With this change, those workflows continue to run, and your endpoint receives the request even when the payload is based on an older configuration.

## What you need to do

Your action’s endpoint may now receive payloads that don’t exactly match the action’s current configuration, but instead match a previous version that merchants are still using in their workflows. Make sure your endpoint can safely handle:

* Missing fields that have become required in newer versions
* Extra fields that existed in older versions but have since been removed
* Any other unexpected fields or schema differences

Typical strategies include applying sensible defaults for missing fields, ignoring unknown or legacy fields, or returning a clear error response when the payload can’t be processed safely.

For more details on how requests are sent and executed, see [Flow action execution](https://shopify.dev/docs/apps/build/flow/actions/endpoints#flow-action-execution).