ST-2026-050 · SDKs, clients & toolchains
Shopify Flow tolerates added and removed action fields at runtime
Shopify Flow API 2026-07 keeps older action configurations running when fields are added or removed, while field-type changes remain breaking.
Shopify Flowaction extensionsschema compatibilityAPI 2026-07
Previous state
Action-schema additions or removals could prevent older workflow configurations reaching the partner endpoint.
Current state
Older configurations continue executing with missing, extra or legacy fields; partner servers must tolerate the resulting payloads.
Affected users
Who needs to care
Partners operating Shopify Flow action-extension endpoints.
Required response
What to do
Handle optional, extra and legacy fields defensively and continue treating field-type changes as breaking.
Evidence boundary
What the source does not prove
Compatibility applies to added and removed fields, not field-type changes or arbitrary endpoint contract changes.
Lifecycle history
Dated event sequence
- Compatibility documented
Older action configurations gained the bounded runtime compatibility behaviour.
Evidence ledger
First-party sources
- 01Shopify Developer Changelog — Shopify Flow changes to action extensions result in fewer breaking changes
Official developer changelog · 2026-07-07
Open official source ↗