Lookbacks at minute scale show up everywhere support actually works. A ticket timestamps the outage at 9:30 and someone asks when monitoring first blinked if the lag was forty-five minutes. A meeting recap says the decision landed at 3:15 and you need when the debate started. A student log says the upload failed "about an hour ago" but the LMS row is exact—you want forty-five minutes before that row, not a guess from the wall clock.
The form subtracts whole minutes from one anchor datetime and prints the earlier calendar line. It sits between second-level log windows and time-ago, which is for longer hour-and-minute blocks. No timezone conversion; match the zone on the export before you paste into a query.
45 minutes before May 9, 2026 at 9:30 AM is 8:45 AM the same morning—easy to flip with forward math and land on 10:15 if you were on autopilot.
"About an hour ago" is not a filter
Chat rounds; databases do not. Running the reference once beats subtracting in your head when the minutes column is :07 or :52. Sub-minute windows belong on seconds-ago—45 seconds before that same morning stamp. Heavier spans with hours in the rule fit time-ago—3 hours 20 minutes before that anchor—instead of stacking one hundred eighty minutes here.
Going backward still moves the date near midnight. 90 minutes before May 10 at 12:30 AM is 11:00 PM on the ninth; titles still say the tenth sometimes. Forward reminders use the other page—45 minutes after the same 9:30 AM stamp—not subtraction on this form.
- Reference datetime is the event named in the note, not "now" unless you set it.
- Confirm you stepped back; forward results look fine until the search is empty.
- Keep anchor plus minutes beside the answer for the thread later.
Whole calendar days without a clock time belong on days-ago. When UI labels fight exported values, the audit trail time-ago note still applies at minute granularity. Ordinary reference math, not legal advice.