All changelog posts

• Oct 9, 2025

  Throttle Step

  The new Throttle Step allows you to limit the frequency of a workflow execution for each subscriber within a specified time window. This will prevent duplicate or excessive notifications across all channels. You can use fixed or dynamic windows. Perfect for managing high-frequency alerts, cron jobs, or multi-project notifications.

  Author:

  Dima Grossman

  • Workflow Steps
  • Improvement

  

  The new Throttle step in the Novu workflow editor allows you to limit the number of notifications a subscriber receives within a specified time frame, ensuring they receive the right amount, neither too many nor too few.

  When a trigger fires repeatedly (e.g., from cron jobs or high-frequency alerts), throttling ensures that subscribers don’t receive duplicate messages across any channel.

  

  You can now:

  • Configure throttling directly in the workflow editor.
  • Define Fixed or Dynamic throttle windows.
  • Limit executions by subscriberId or add a secondary grouping key from your payload (e.g., payload.projectId).
  • Prevent notifications from executing beyond your defined threshold (even for critical workflows).
  • Transparently control frequency across all channels (email, in-app, SMS, chat, push).

  Configuration options:

  • Fixed window: Set a predefined duration (e.g., “1 per hour”) with an execution threshold.
  • Dynamic window: Define flexible time ranges using trigger payloads (payload.throttleUntil or payload.customWindow).
  • Group throttling by: Combine subscriber and payload-level keys for granular control (e.g., per project or account).

  Learn more by visiting the Throttle Step documentation →

  Improvements (3)

  • Schemas now support null values for optional fields in workflows, ensuring executions no longer fail when data is intentionally unset.

  • Add support for excluding specific subscribers from topic-triggered workflow fanouts using an optional exclude array.

  • Add support for defining a custom display order of workflows in the Preferences UI, allowing prioritized workflows to appear at the top.

  Fixes (1)

  • fix(dashboard-ui): Unify and align all dashboard tables (Workflows, Subscribers, Topics, Topic Subscriptions) using the new OriginUI table component for consistent layout, pagination, and record visibility.

• Oct 6, 2025

  Scheduled Delay

  Schedule your workflows with precision - pause until the exact minute, hour, or weekday in each subscriber’s local time, and even align delivery with their working hours.

  Author:

  Paweł Tymczuk

  • Workflow Steps
  • Delay

  

  You can now schedule workflow pauses using an intuitive time selector - allowing you to delay messages until an exact time, day, or week in your subscriber’s local timezone.

  

  This new Scheduled Delay option (when configuring the Delay step) provides developers with fine-grained, time-aware control over workflow timing, allowing you to match your subscribers’ schedules, respect working hours, and ensure messages arrive at the optimal moment, not just after a fixed interval.

  What you get:

  • Two delay modes: choose between
    • Regular Delay: wait a fixed duration (e.g. “5 minutes”)
    • Scheduled Delay: wait until a specific time or date pattern
  • Flexible scheduling options:
    • Until minute — delay until the next minute mark
    • Until hour — at X minute(s) of the hour
    • Until day — at X hour(s) : X minute(s)
    • Until week — choose one or more days (Mon–Sun) at X hour(s) : X minute(s)
    • Until month — choose specific day(s) of the month and time of day
  • Time zone–aware delivery: All delays are evaluated and executed in the subscriber’s local time zone.
  • Working hours support: toggle “Extend to subscriber’s schedule” to automatically hold delivery until the subscriber’s next available time window.
  • Configurable limits: by default, delays can extend up to 1 day (contact support to extend for longer intervals)

  Example use cases:

  • Send a weekly digest every Friday at 9:00 AM subscriber local time.
  • Deliver a trial reminder at 8:00 AM on the day of expiry.
  • Respect user schedules by delaying notifications until working hours.

  How to use it:

  In the workflow editor → add a Delay step → select “Scheduled” → configure your timing (minute, hour, day, week, or month) and enable “Extend to subscriber’s schedule” if needed.