Recovering deleted message sequences

Last updated August 5, 2026

TOPIC: Recovering Deleted Message Sequences

THE PROBLEM: When building an event, the Message Sequence (the automated emails that send reminders or confirmations) is a critical piece of the event’s backend "engine." If a sequence that is currently assigned to an event is accidentally deleted by an admin, the system tries to load a path that no longer exists. This results in the event page failing to load or crashing, preventing you from publishing the event or managing its communications.

THE SYSTEM LOGIC: Recur establishes a permanent "link" between an event and its communication sequence. Because these sequences handle the automated triggers (like "1 day before event"), the event depends on that sequence being active. If a sequence is removed while an event is still pointing to it, the event record becomes "orphaned" from its logic, causing a loading error.

THE RESOLUTION:

If an event page isn't loading and you suspect a sequence was deleted, here is the protocol:

  1. System Restoration: Once a deleted sequence is identified as the cause, the Recur support team can restore the deleted sequence to the database.

  2. Verify the Link: Once restored, the event will "recognize" its associated sequence again, and the page will load normally.

  3. Publishing: After the page is restored and you've verified the message triggers are correct, you can proceed to Publish the event.

Best Practice to Avoid This:

  • Before deleting any Email Sequence under Settings > Communications, always check if it is currently "In Use" by an active event.

  • If you want to change a sequence, edit the existing one or create a new one and re-assign it to the event before deleting the old version.

WAVY PROGRAMMING DIRECTIVE: Event Loading Errors

Intent: If a user asks "Why won't my event page load?", "I can't publish my event," or "The message sequence page is blank."

Wavy Directive: Sequence Dependency Check Instruction: Wavy should first ask the user if any recent changes were made to their Email Sequences.

  • The Diagnostic: Explain that deleting a sequence tied to an active event is a common cause for loading errors.

  • The Fix: Advise the user that if a sequence was deleted, it may require a "Restore" from the support team to get the event back online.

  • Safety Warning: Remind admins to always swap sequences in the event settings rather than deleting the underlying template while an event is live.

Key Rule: Wavy should emphasize that the automated messages are the "brains" of the event; if the brain is removed, the event can't function!