> For the complete documentation index, see [llms.txt](https://guides.stellaraio.com/stellar/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-tasks-tab.md). # Tasks Tab Create, organize and manage tasks in Stellar AIO 4.0, from your first task group to bulk edits and task statuses. The **Tasks** tab is where you create, organize and control the jobs Stellar runs for a retailer. A task follows the settings you give it, such as which product to monitor, which profile to use and which checkout mode to run. This guide covers the shared controls in **Stellar AIO 4.0**. Use your retailer’s guide for the correct mode, product format, proxies, delays and drop preparation. ![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQL0BOlyqRRf7zyNKSf%2Fuploads%2Fu9q0WfY0XGsGApEjlcZb%2Fclipboard.png?alt=media\&token=9670f2e0-7de4-4ff9-928f-80824aac20a2) Stellar AIO 4.0 Tasks tab showing task groups, toolbar and a filtered task list *Example: a Target group with Search tasks set to monitor. These settings illustrate the interface; they are not universal retailer recommendations.* ### Understand groups, tasks and modes * **Task group:** A named collection of tasks for one retailer. Use clear names to keep different setups organized. * **Task:** One configured job inside a group. Creating it saves the setup; starting it tells Stellar to run it. * **Mode:** The type of job the task performs. Depending on the retailer, a mode may monitor stock, log in or attempt checkout. Not every task is a checkout task. **Example:** A Target group can contain Monitor tasks and Shipping tasks. They have different jobs and fields even though they belong to the same group. Follow the [Target guide](https://guides.stellaraio.com/stellar/retailers/target) for how they work together. ### 1. Create or select a task group 1. Open **Tasks** in the sidebar. 2. Select the **+** beside **MY TASK GROUPS** to open **New Task Group**. 3. Use **Search Sites** to find the retailer, then select its card. 4. Enter a recognizable **Group Name**, then select **Add**. 5. Open the retailer folder on the left and select your group. ![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQL0BOlyqRRf7zyNKSf%2Fuploads%2FWlKgbH91zHn5zouNaCob%2Fclipboard.png?alt=media\&token=097dea6d-9a95-4d0b-82b4-ff6e15da0be0) New Task Group form with Target selected and an example group name If **Create Task** is unavailable, make sure you have selected an actual task group inside the retailer folder. Selecting the retailer folder alone is not the same as selecting a group. ### 2. Create tasks Select **Create Task** in your chosen group. Choose the **Mode** recommended in the retailer guide; selecting a mode reveals the fields needed for that job. ![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQL0BOlyqRRf7zyNKSf%2Fuploads%2F3Q580qPaE49D9v4w7WP2%2Fclipboard.png?alt=media\&token=d1bac7e5-cb37-4eb5-8e4f-940d10a2cd05) Stellar 4.0 New Task form before selecting a mode * **Name:** A label to help you recognize the task. * **Mode:** What the task will do. Available modes depend on the retailer. * **Profile:** The saved checkout details the task should use, when required. Prepare your profiles before setting up checkout tasks. * **Monitor Proxy / Checkout Proxy:** The proxy groups used for the relevant connections. The fields and requirements vary by mode; follow the retailer guide instead of assuming every task needs both. * **Product fields:** These may use a URL, SKU, Input List or another retailer-specific format. A SKU is an identifier for a product. Use the format required by that retailer and mode. * **Delays:** Timing settings for the task’s requests or retries. Use the retailer’s recommended values. * **Qty at the bottom of the creation form:** Controls task creation quantity. Do not confuse it with a product quantity field shown inside a retailer’s settings. Review the settings, select **Create**, and check the new rows in the task list before starting them. ### 3. Find and select the tasks you need The search box beside the group list helps you find groups. **Search tasks** above the task list helps you find matching tasks, such as a mode, SKU, profile or proxy name. Use the checkbox beside a row to select it. The statistics area shows a **Selected / Total Tasks** count when tasks are selected. Clear selections you no longer intend to act on. **Check the scope before applying an action:** Confirm which group is highlighted and which task rows are selected. Search narrows what you see; do not treat it as a substitute for selecting the tasks you intend to change. Use actions explicitly labeled **Selected** when you want to target selected rows, and read the task count shown in an edit or confirmation dialog. ### 4. Start, stop and manage tasks #### Group controls * **Start All:** Start tasks in the current group. Choose the correct group and review the setup first. * **Stop All:** Stop tasks in the current group while keeping their saved configurations. This is the current label for the control older guides may call End All. * **Edit All:** Open the bulk editor for the current group. See the walkthrough below. * **Delete All:** Remove tasks from the group. This replaces the older Clear All wording. Use Stop All if you only want to stop running tasks and keep the setup. #### Selected tasks and individual tasks The arrow beside **Start All** includes **Start Selected** and **Restart Selected**. The arrow beside **Stop All** includes **Stop Selected**, and the arrow beside **Delete All** includes **Delete Selected**. You can also select the intended task rows and right-click to open their action menu. Check the **Selected … task(s)** count at the top. Common actions include: * **Start / Stop:** Run or stop the selected tasks. * **Restart:** Restart the selected tasks. Follow the retailer guide before restarting tasks that are in a queue or active checkout. * **Edit:** Change the selected task setup. * **Duplicate:** Make a copy of the selected tasks. Review the copies before starting them. * **Move to Group:** Organize tasks into another available group. * **Delete:** Remove the selected tasks. Other actions, such as Watch Task and cookie controls, depend on the retailer. Use its guide before changing those settings. ### 5. Edit multiple tasks with Edit All 1. Select the group you want to update and choose **Edit All**. 2. Read the message showing how many tasks the edit covers. 3. Use **Select Mode** to choose all modes or a specific mode. Choosing one mode reveals its additional fields. 4. Enter only the values you want to change. **Fields left empty are not overwritten by default.** 5. Review the mode, task count and changed fields, then select **Save**. ![](https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MQL0BOlyqRRf7zyNKSf%2Fuploads%2F4uc6LXWmRQsF2TJQ15Hz%2Fclipboard.png?alt=media\&token=166b2d7c-81f1-416b-b19b-d37f868dde3c) Edit All Tasks dialog showing task count, mode selection and empty-field behavior **Example:** In a group with Target Monitor and Shipping tasks, choose **monitor** if you only want to update the Monitor tasks. Do not leave the mode set to All when the change is intended for only one mode. Whether a change can be made while tasks are running depends on the retailer and setting. The [Pokémon Center guide](https://guides.stellaraio.com/stellar/retailers/pokemon-center) includes the confirmed Guest-task mass-edit walkthrough for changing products while remaining in queue. Do not assume that behavior applies to every mode. ### Read task status and statistics The summary above the list shows counts such as **Total Tasks**, **Running Tasks**, **Added to Cart** and **Checkouts**. Some retailers show extra information, such as cookies. Check each row’s **Task Status** to understand what it is doing. If the list is wider than the window, scroll horizontally to see columns and actions further to the right. * **Idle:** The task is not currently running. * **Monitoring or waiting:** The task may be waiting for stock, a queue or another required step. Read the exact status and retailer guide before restarting it. * **Error or repeated retries:** Review the exact message, product input, profile/account, proxies and any required harvesters. Different errors need different fixes. Added to Cart does not mean checkout is complete. Check the task result and the retailer’s order confirmation to verify an order. ### More tools: import, export and logs Open **More** above the task list for additional group tools. The options shown can vary by retailer. * **Export Group to JSON:** Save the group’s task configuration to a file for reuse. * **Import Group from JSON:** Load an exported group configuration. Review the resulting tasks and their profile, account and proxy selections before starting. * **Log Summary:** View information that can help explain task activity and troubleshoot issues. * **Restart All:** Restart the group’s tasks when appropriate for that retailer’s workflow. * **Webhook Settings:** Configure the available notification settings for the group. Keep exported files private if they contain account or setup details. A task export should not be treated as a backup of every setting in Stellar. ### Monitoring and retailer-specific preparation Monitoring means checking whether a product is available. Some retailers use dedicated Monitor tasks; others check availability within their checkout modes. Follow the retailer guide for which tasks to create, how they work together and when to start them. Instructions for Stellar’s old built-in server-side monitor no longer apply. Use the current retailer setup instead of relying on an older video or monitoring workflow. ### Rename or delete a task group In the group list, right-click the group you want to manage. Choose **Rename** to change its label or **Duplicate** to make a copy. To remove a group, stop its tasks, right-click the group and choose **Delete**. Check the group name and confirmation before continuing. Export the group first if you may need its configuration again. Use **Stop All** instead when you only want to stop tasks and keep them. ### Before your first run * Confirm the correct group, retailer and mode. * Check product inputs, product quantities and any price limits offered by the mode. * Verify profiles, accounts and proxies required by that retailer. * Prepare [Captcha or Shape Harvesters](https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-harvesters-tab) if the retailer guide requires them. * Follow the latest drop instructions for when to start tasks. If you need help, share the retailer, mode, exact status and what you have already tried with Stellar support. Hide account details, payment information and proxy credentials in screenshots. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://guides.stellaraio.com/stellar/navigating-stellaraio/what-is-the-tasks-tab.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.