> ## Documentation Index > Fetch the complete documentation index at: https://moengage.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # What Happens to Users Queued on a Delay Condition When an Event-Triggered Campaign Is Edited? > Editing a live event-triggered campaign with a delay condition creates a new campaign version. Users already queued on the retired version are dropped, not sent the old or new content. ## Scenario An event-triggered campaign uses **With Delay** to send a message a set time before or after a trigger event, using either a fixed time value or an event attribute (for example, a *flight\_time* attribute). While users have already triggered the event and are queued waiting for the delay condition to be met, the campaign's content is edited and published. ## Behavior * Editing and publishing a live event-triggered campaign creates a new [campaign version](/docs/user-guide/campaigns-and-channels/campaign-management-and-reports/campaign-versioning) — a new campaign ID, with the previous version retired. * Users who triggered the event before the edit are queued against the retired version, not the new one. * When the delay condition matures for these queued users, they are dropped. They do not receive the retired version's content or the newly published content. * Only users who trigger the event after the new version is published are eligible to receive the updated content. * This applies to any **With Delay** configuration, whether the delay uses a fixed time value or an event attribute. It does not apply to campaigns configured to trigger **Immediately**. To avoid dropping queued users, publish content changes to a live event-triggered campaign that uses **With Delay** only after existing delay windows have closed.