META OCT27 MATRIX

Use cases

Three concrete situations where teams use this matrix before the all-versions date.

Pinned mobile SDK still sending date_format

Who: A mobile engineer whose app dashboard still lists an older Graph version.

Task: Confirm whether pinned clients escape the 27 October legacy protocol errors.

Steps: Select “pinned = safe” and “legacy = yes” on the matrix, copy the date_format search string, scan the SDK wrapper and any shared networking module, remove the parameter, and convert timestamps locally.

Result: A tracked ticket with evidence the loud error path is gone before cutover week.

n8n Facebook Graph node with custom query params

Who: An ops engineer maintaining n8n workflows that talk to Pages or Insights-adjacent calls.

Task: Find workflow nodes that will start returning parameter errors.

Steps: Open the matrix with legacy=unsure, copy the search list, grep exported workflow JSON for date_format and ids parameters, rewrite nodes to omit them, and schedule a log review on 27 October.

Result: Automation continues without a surprise failure storm on cutover morning.

Instagram checkout order sync with no replacement

Who: A shop engineer still pulling commerce_orders into an internal OMS.

Task: Decide what breaks when Commerce Order Management disappears from remaining versions.

Steps: Mark commerce=yes, copy the commerce checklist, inventory every job that hits those endpoints, and open a product decision for post-Graph order intake.

Result: Stakeholders see that this is not a rename — it is a sunset with operational consequences.