Some deadlines are literally in seconds. A queue message says retry after thirty. A stream key expires in ninety. A lab instrument wants the next readout forty-five seconds after the logged start, not "about a minute" in Slack. You already have the anchor datetime; you need the exact later stamp for a filter, cron row, or paste into another tool. The form adds whole seconds forward from that point and prints the calendar datetime.
That is narrower than the time-from-now page, which mixes hours and minutes when the span is longer. Here the unit field is only seconds, which keeps typos out of hour boxes when the rule really is "plus 45 s." No timezone math—match whatever zone the log or API already uses.
45 seconds from May 9, 2026 at 9:30 AM lands at 9:30:45 the same morning, the kind of answer people still sanity-check because mental math on :45 feels easy until the source was :29.
When the clock almost rolls the day
Late-night anchors are where a small second count still changes the date line. 45 seconds after May 9 at 11:59:30 PM is already the tenth, not "still the ninth" in a ticket title. Read the result once before you paste—plenty of folks fix the seconds and miss the day flipped.
Lookbacks use the ago twin: 45 seconds before that same 9:30 AM stamp for log windows, not forward addition here. Once you are past a couple of minutes, 3 minutes from the same anchor is usually less fiddly than typing one hundred eighty in the seconds box.
- Base is the event you are stepping from, not "now" unless you set the picker that way.
- Whole seconds only—fractions belong in the source system, not this form.
- Copy the anchor beside the answer if someone will re-open the thread later.
Product copy loves round minutes; the minutes-from-now reminder note pairs well when UI text and the real timestamp need to agree. Ordinary scheduling math, not legal advice.