> ## Documentation Index > Fetch the complete documentation index at: https://help.lobyco.com/llms.txt > Use this file to discover all available pages before exploring further. # Lifecycle > What a push, email, banner, feed or prompt does at each status, and what you can still change. Every push, email, banner, feed and prompt in a campaign shows one of four statuses: **Draft**, **Scheduled**, **Active** or **Expired**. [Find and manage campaigns](/business-documentation/campaigns/find-and-manage-campaigns) explains how the portal works the status out from the dates. This page says what each communication does at each status, and what you can still change. ## At a glance | Status | What customers get | What you can change | | - | - | - | | [Draft](#draft) | Nothing. A flow that reaches a triggered draft skips it. | Everything. You can also delete it. | | [Scheduled](#scheduled) | Nothing yet. A flow that reaches a triggered one skips it. | Everything. You can also take it back to draft, and some communications let you publish it now. | | [Active](#active) | A push or email goes out. A banner, feed or prompt is shown in your app. | It depends on the communication. | | [Expired](#expired) | Nothing more. Banners, feeds and prompts are no longer shown. | Nothing. You can still view it, duplicate it or save it as a template. | A triggered communication is one whose block is connected after another block on the canvas. [Recipients](/business-documentation/communication/triggering) explains the difference. ## Draft A draft isn't published, so customers don't see it. * **Save** keeps it as a draft. * **Publish** asks you to confirm. If the start date is still to come, the communication becomes **Scheduled**, and active on that date. Otherwise it becomes **Active** straight away. * **Delete** is only offered while it's a draft. * You can only connect or disconnect its block on the canvas while it's a draft. See [Connect the blocks](/business-documentation/campaigns/orchestration-canvas#connect-the-blocks). ## Scheduled A scheduled communication is published, but its start date hasn't come yet. For a push, the start is its **Delivery date**. Customers don't see it yet. * You can still change everything. * **Unpublish** in its form takes it back to **Draft**. On its row in the campaign's **List** view, the menu calls this **Unpublish** for a push or feed, and **Disable** for an email, banner or prompt. * The row menu can also skip the wait. **Send now** sends a push straight away. **Publish now** makes a banner or feed active straight away. An email or prompt doesn't offer this. ![A campaign's List view with one push, Coffee week last-days reminder, whose status is Scheduled, from 2026/11/27 10:00 to 2026/11/29 23:00. The menu at the end of its row is open, with Edit, Send now, Duplicate as draft, Unpublish and Save as template.](https://mintcdn.com/lobyco-4c9fb3ad/rG971_5ZfS49bcjM/images/communication-02-scheduled-push-row-menu.png?fit=max\&auto=format\&n=rG971_5ZfS49bcjM\&q=85\&s=960a142828c267fa8e022824056e9327) *A scheduled push's row menu* ## Active An active communication is published, and today falls between its start and end dates. What it does, and what you can still change, depends on the communication and on whether it's triggered. | Communication | What it does while active | What you can still change | | - | - | - | | Push to a group | Goes out once, at its **Delivery date** | Nothing. You can't edit or unpublish it. | | Triggered push | Goes to each customer the flow sends to it, until its **Expiration date** | Everything except the **Delivery date**. You can't unpublish it. | | Email to an audience | Goes out once, at its **Start date** | Nothing. You can't edit or unpublish it. | | Triggered email | Goes to each customer the flow sends to it, until its **End date** | Everything except the **Start date** and **End date**. You can unpublish it from its form. | | Banner | Shown in your app until its **End date**. A triggered one is shown to each customer for their validity period. | Everything except the **Start date**. You can unpublish it. | | Feed | Shown in your app until its **End date**. A triggered one is shown to each customer for their validity period. | Everything. You can unpublish it. | | Prompt | Shown in your app until its **End date**. A triggered one is shown to each customer for their validity period. | Everything. You can unpublish it. | When you save changes to an active push, banner, feed or prompt, the portal asks you to confirm, because customers see the changes straight away. Unpublishing asks you to confirm first. It takes the communication back to **Draft**, and no new customers get it. A banner, feed or prompt stops being shown. Customers who already got a push or email keep it. ## Expired An expired communication's end date has passed. For a push, the end is its **Expiration date**. * Nothing more goes out, and banners, feeds and prompts are no longer shown. A flow that reaches a triggered one skips it. * Its form is read-only. On its row in the campaign's **List** view, the menu offers **View** instead of **Edit**. * **Duplicate as draft** makes a new draft copy that you can change and publish. **Save as template** is still there too. When the campaign itself ends, all its activities become read-only, whatever their own status. ## Change the dates on the canvas Each communication's block on the **Orchestration** canvas shows its status and its **Start** and **End** dates, plus the **Validity period** of a triggered banner, feed or prompt once you've set one. While the communication is a draft or scheduled, you can change these right on the block. An email's dates only change on the block while it's a draft. A change you make on a block is saved straight away. ## Related * [Recipients](/business-documentation/communication/triggering) — picking customers, and how a triggered communication behaves. * [Find and manage campaigns](/business-documentation/campaigns/find-and-manage-campaigns) — how a status is worked out from the dates, and filtering activities by status. * [Orchestration canvas](/business-documentation/campaigns/orchestration-canvas) — connecting communication blocks, and when changes are saved. * [Communication](/business-documentation/communication) — how to create each communication, step by step. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.