See what still breaks on 27 October even if you pinned an old Graph API version.
For teams integrating Meta Graph or Marketing API. Answer whether you rely on legacy protocol, commerce orders, or Marketing estimate/story/poll surfaces. Get a path, grep strings, and a ship checklist — local only.
Pinned ≠ safe
The all-versions entries land on every remaining version the same day. This matrix kills the false “we stayed on v24” comfort.
Loud vs quiet failures
date_format and root /?ids= become errors; pretty/debug/ETag and some Marketing fields fail silently — checklist both.
Commerce with no replacement
If you still call commerce_orders family endpoints, the path is business shutdown planning, not a rename.
Open the Oct 27 matrix
Select pin / legacy / commerce / Marketing. Copy path + search strings.
How to run it
Eight steps from changelog skim to log review on cutover week.
Use cases
Pinned SDK shop, n8n date_format node, Instagram checkout sync sunset.
FAQ
Upgrade Tool vs this matrix, batch response shape, what we are not.
What the 27 October cutover covers (for implementers)
- Legacy protocol — date_format and GET /?ids= error; pretty/debug ignored; If-None-Match/ETag/304 removed.
- Commerce Order Management — ~47 endpoints removed from remaining versions; Meta states no replacement.
- Marketing — delivery_estimate field drops; messenger story silently removed; poll creatives rejected.
- Not covered — unrelated v26 feature launches, Page Insights June precedent details beyond a reminder to re-test dates.
Not affiliated with Meta. Re-read the live Graph API changelog and developer blog the week you ship.