Elmstone Logistics keeps delivery requests in a SharePoint list and packing rows in an Excel table. The names are similar, but the objects have different jobs. Read the destination in each prompt before choosing a connector. A successful write to the wrong object still fails the business request.
You will reuse list counts, row creation, keyed updates and notifications. Each event has a different identifier or recipient in the hidden fixture. Preserve those references as text, including leading zeros. The diagnostic questions revisit missing tables, duplicate keys and connector boundaries. Use the recorded effect after a write to check that its destination, key and retained columns all match the task, especially when the visible sample contains only one row.