> ## 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. # Find and manage campaigns > Find a campaign in the list, control when it runs, read what happened when it ran, and remove it. Once a campaign exists, this is where you find it again, control when it runs, and check what it did. Read on for the list itself, how to schedule its runs, and how to read an execution. ## Find a campaign Campaigns are listed under **Campaigns → List**. Each row shows the campaign name, the number of activities in it, **Type**, **Start date**, **End date**, **Status** and **Edited by**. There is no search box on the list. Searching and filtering both live in a panel that is collapsed by default — open it with the filter icon above the list, a button with an icon and no text label. Inside it, the box placeholdered **Name of activity or campaign** matches a campaign name or an activity name, and **Status** filters by status. A campaign row shows one of three statuses: | Status | Meaning | | ------------- | -------------------------------------- | | **Scheduled** | Its start date is still in the future. | | **Active** | It has started and has not ended. | | **Expired** | Its end date has passed. | **Draft is a fourth status, and it belongs to activities.** The same badge shows **Draft** on an activity row inside a campaign, for an activity that has not been published. A campaign row never shows it. The status filter offers all four — Active, Scheduled, Draft and Expired. **Where:** Campaigns → List **Must show:** The list with its columns, and the filter panel expanded so the name box and the four status options are visible. **Why this shot:** The status vocabulary and the location of the filter are the two things a reader needs from this screen, and the filter is behind an icon-only button that is easy to miss. *Placeholder — replace with the image once captured. 1440px, light theme, test data only.* ## The Calendar view **Calendar** is one of three views on the campaign list, alongside **List** and **Orchestration**. It draws campaigns as bars across a single month, one row per campaign, with each campaign's activities as child rows you can collapse. A vertical line marks now. A bar is drawn only where both dates exist, so an activity missing either one gets a row and no bar. Hovering either the bar or the campaign name opens a tooltip with **Start date**, **End date** and **Status**; activity rows add **Type**, campaign rows do not have one. Where a bar runs outside the month on screen, a marker at the edge says how far away it is and jumps you there when clicked — *← 2 weeks ago* on the left, and on the right either *In 3 days →* for a bar that has not started yet or *3 days more →* for one that starts this month and continues past it. A bar that starts before the month gets the left marker even when part of it is visible. Distances round up to whole weeks from seven days, and never read less than *1 day*. **Where:** Campaigns → **Calendar** **Must show:** The month selector, the week and day header rows, the now line, one campaign row expanded to its activity children, and one edge marker for a bar running outside the month. **Why this shot:** The parent-and-child row structure and the edge markers are the two things nothing in the text can convey. *Placeholder — replace with the image once captured. 1440px, light theme, test data only.* **The calendar draws a capped number of campaigns.** Above that cap it says so — *Only the first N of M campaigns are displayed. Use filters to narrow your search.* Filter rather than assuming a campaign is missing. ## Schedule when it runs A saved campaign does nothing until something triggers it. Open the campaign's orchestration canvas and use **Scheduled runs**. Triggers are listed in one table, with the columns **Title**, **Job type**, **ID**, **Created At**, **Runs from**, **Runs to** and **Frequency**. **Frequency** is where you read the schedule itself: a recurring trigger spells out how often it repeats, a one-time trigger reads **Run once**. Add one with **Create new run**. Give it a **Job name** and a **Job type**, then choose a **Schedule type**: **One-time** or **Recurring**. A one-time trigger takes a single **Start date**. A recurring trigger takes a **Frequency**, a **Start date** and an **End date**; leave the end date empty and the trigger is open-ended, which the list shows as **No end date**. Both display the **Time zone** the run will use. **A recurring trigger shows you when it will next fire.** As you set the frequency, the form lists the upcoming run times underneath it, with **Show more runs** to see further ahead. Use it to check a frequency does what you expected before saving — a schedule that reads correctly can still fire at the wrong time. Selecting a trigger already in the list shows the same preview under **Next runs**. Until you add one, the campaign says **No runs created yet.** ## Read an execution Every run appears under the canvas in **Executions**, newest first, with the columns **Job type**, **ID**, **Status**, **Started at**, **Ended at**, **Result summary** and **Executed by**. An execution carries one of nine statuses: | Status | Meaning | | --------------------- | ------------------------------------------------------- | | **Checking** | The portal is still fetching this run's status. | | **Scheduled** | Queued to start at its scheduled time. | | **Pending** | Created, not started yet. | | **In progress** | Running. | | **Done** | Finished cleanly. | | **Done with warning** | Finished, but something needs looking at. | | **Failed** | Did not complete. | | **Terminated** | Stopped before finishing. | | **Cancel requested** | A stop has been asked for but has not taken effect yet. | **Skipped is a block status, not a run status.** It appears on a single block inside a run that did not execute. A run itself never reads Skipped. **Done with warning is not the same as Done.** It means the run finished and produced a result, but reported something along the way. Read the **Result summary** column for what it reported — a run can complete and still have dropped customers. Open a run to see the campaign it belongs to, **Executed by** — who started it, as against **Edited by** on the campaign list, which is who last changed the campaign — the execution ID, its status and progress, and when it started and ended. A run that produced files lists them at the bottom under **Execution results**. ## Remove a campaign Delete a campaign from the row menu on the list. **Delete** is disabled while the campaign still holds activities — its tooltip reads *To delete campaign you need to delete all activities first* — so delete the activities before the campaign. The confirmation reads **Are you sure you want to permanently delete this campaign?** / **This action cannot be undone.**, with **Cancel** and **Delete**. It does not name the campaign, so check you opened the menu on the right row. Removing a trigger is separate and asks separately — **Are you sure you want to remove this trigger?** Deleting a scheduled run leaves the campaign itself in place. ## Troubleshooting ### The campaign is saved but has never run Check **Scheduled runs**. A saved canvas with no trigger will sit indefinitely; it says **No runs created yet.** when that is the case. ### A run finished but fewer customers came through than expected Check the run's status first — **Done with warning** points at errors during the run. Then check the canvas for an **Enrich** block dropping customers with no result, or a **Limit** block that has hit its cap. Limits that reset per day or per week will already have consumed part of their allowance. ### I can't find the search box There isn't one on the list. The name box is inside the filter panel, which starts collapsed — open it with the filter icon above the list. ### Delete is greyed out on a campaign The campaign still has activities in it. Delete those first; the tooltip on the disabled item says the same. ## Related * [Orchestration canvas](/business-documentation/campaigns/orchestration-canvas) — building and connecting the blocks a campaign runs * [Schedule and run a campaign](/business-documentation/campaigns/schedule-and-run-a-campaign) — setting the dates and runs from scratch * [Block reference](/business-documentation/campaigns/block-reference) — every block, what it needs, and what it passes on