A sequence step only fires if its send time is in the future. Remindax computes each step's send time from the expiration/due date, the "days before/after" value, and the send time you set. If that computed moment has already passed, the step is skipped and you'll see: "Reminder may not be sent because the reminder date/time is in the past." This is expected — it's Remindax telling you that step can't fire, not that something is broken.

How a step's send time is computed

Each step combines three things:

  1. The item's date (expiration or due date).
  2. The offset — a number of days, before or after that date.
  3. The send time — e.g. 1000 HRS (10:00 AM) in the sequence's time zone.

Example: expiry = June 30, step = "30 days before" at 1000 HRS → the step is scheduled for June 1, 10:00 AM. If today is already past June 1, that step won't fire and you'll see the warning.

When you'll see the warning

  • The item expires soon, but a step is set for a large "days before" value (e.g. "60 days before" on an item expiring in 10 days — the 60-day mark is already behind us).
  • You imported or created an item close to (or after) its expiry date, so the earlier steps are already in the past.
  • You edited the expiry date to something nearer, moving some steps into the past.

How to fix it (only if you want that notification to go out)

  • Reduce the offset so the send time is in the future (e.g. change "60 days before" to "3 days before").
  • Use an "after" step to notify following the date instead.
  • Adjust the expiration date if it was set incorrectly.
  • Or do nothing — later, still-future steps in the sequence will send normally.

What happens next

  • Steps whose send time is still in the future will send at their set time.
  • Skipped past-dated steps simply don't fire; they don't error or retry.

Edge cases & gotchas

  • All steps in the past = nothing sends. If every step is behind the current date, the item won't notify anyone. The cleanest restart is to duplicate the item with a new future expiry date.
  • Time zone matters. "In the past" is judged in the sequence's time zone, not the recipient's.
  • This warning is about timing only — it's unrelated to whether the item's status allows sending. An Expired/Completed/Inactive/Archived item won't send regardless. See Notifications didn't send.

Related questions

  • What does "may not be sent because the date is in the past" mean? That step's send time has already passed, so it's skipped. Expected.
  • Is this a bug? No — it's a heads-up that the step can't fire.
  • How do I make it send anyway? Reduce the "days before" offset, use an "after" step, or fix the expiry date.
  • None of my steps will send — why? They're all past-dated. Duplicate the item with a new future expiry date.

Related articles

How notifications & sequences fit together · Notifications didn't send · Error message reference