changelog
Mimeo 0.3.3: ever or in the last N days, and switches that act the same everywhere
Every rule that looks back in time now asks for "ever" or "in the last N days", and turning sequences, steps and guards on or off acts the same from every path.
Version 0.3.3
Improvements
- Every rule that looks back in time (engagement, events and sequence history) now asks you to choose "ever" or "in the last N days", and the days box can't be left blank. This covers segments, guards, flow branches, gates, triggers and subscription preferences. See Segments.
- An "in the last N days" window must be a whole number of days, 1 or more, wherever a rule is saved, including through the API, MCP and
mimeo push. Leaving it out still means ever. See conditions. - Guard conditions are now checked when you save them in the app, over the API or through MCP, the same way segments and pushed guards already were. See Guards.
- The segment and flow-building agent skills in your manager repo now explain that leaving out the days window means ever.
Fixes
- Turning a sequence back on with
mimeo pushnow releases the emails held while it was off, instead of leaving them held. See Sequences. - Switching a sequence step between active and draft in a pushed sequence file now adds it to or removes it from the plans of people already partway through, as the sequence page does.
- Turning a guard off by saving it, or deleting it, now releases what it was holding straight away.
- Emails waiting on a turned-off sequence or a paused flow now always show that reason in the queue.
- Rule summaries now say "any email" when no email is picked, and "ever" or "in the last N days" on every rule that looks back in time, including received, opened and clicked rules.