Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mileapp.dev/llms.txt

Use this file to discover all available pages before exploring further.

When a task is created from a Flow that contains a Subflow component, the system automatically creates one or more subtasks linked to the main task. This guide explains how main tasks and subtasks appear in the Task list, how data flows between them, and how to assign, move, edit, and delete them.

Understanding Main Tasks and Subtasks

  • Main task — the task created from a Flow that contains a Subflow component.
  • Subtask — a task created automatically from each Subflow component on the main task’s Flow.
  • Field mapping — when the main task is created, values from mapped fields are copied to the matching fields in each subtask.
A main task can have one subtask or several, depending on how many Subflow components the Flow has. Subtasks always belong to a main task and cannot exist on their own.

How Subtasks Are Created

When you create a task from a Flow that contains Subflow components, the system does the following automatically:
  1. The main task is created from the Flow as normal.
  2. For each Subflow component in the Flow, a separate subtask is created from the referenced child Flow.
  3. Mapped fields are copied from the main task to each subtask.
  4. Each subtask is linked to the main task, and the main task tracks every subtask it owns.
  5. Subtasks inherit the main task’s assignee, hub, start time, and end time. If the main task already has an assignee, the subtasks start with status Ongoing.
Subtasks cannot be assigned, moved, or scheduled on their own. These changes must be made on the main task, and they are applied to every subtask automatically.

Viewing Main Tasks and Subtasks in the Task List

Desktop

In the Task list, a main task appears as an expandable group header showing the main task’s flow name and a count of its subtasks. Click the header to expand or collapse the subtask rows beneath it.
Task list main task and subtasks

Task list showing main tasks as expandable groups with their subtasks indented below

The expanded view shows:
  1. Flow column — the Flow name of each task; the main task header shows the parent Flow, each subtask shows its own child Flow.
  2. Task selection checkbox — selecting the main task automatically includes all its subtasks in bulk operations.
  3. Status indicator — shows the current status of each task (Unassigned, Ongoing, Done).
  4. Action button — opens the action menu for the row. The available actions depend on whether the row is a main task or a subtask.
Task list desktop view

Desktop view of the Task list with a main task expanded to reveal its subtasks

Mobile View

On mobile view, main tasks appear as expandable card groups. Tap the group header to expand or collapse the subtask cards. Each card shows the Flow name, status, and assignee.
Task list mobile view

Mobile view of the Task list rendering main tasks as expandable card groups

Bulk Operations

Selecting a main task in the Task list automatically includes every subtask in the operation. Bulk operations are accessed through the Action button above the list.
Bulk actions menu

Action menu showing bulk operations available for selected tasks

Available bulk actions:
  • Assign — assign a user to selected tasks.
  • Unassign — remove the assignee from selected tasks.
  • Move — move selected tasks to another hub.
  • Delete — delete the selected tasks.
When the selected row is a main task, the operation runs against the main task and is propagated to all its subtasks. See the per-operation sections below for the restrictions that apply.

Viewing Main Task Details

Opening a main task shows the main task data plus a summary of its subtasks.
Main task detail

Main task detail showing the main task data alongside its subtasks

The detail includes:
  • Basic information — title, content, assignee, start and end time, hub.
  • Subtask list — every subtask with its Flow name and current status.
  • Status — the main task’s own status (Unassigned, Ongoing, Done).
  • Flow data — field values captured on the main task.
Subtask detail

Subtask detail showing its data and its link back to the main task

A subtask’s detail shows the data captured on the subtask itself, including any fields that were copied from the main task through field mapping.

Assigning Main Tasks

When you assign a user to a main task, the assignment is applied to every subtask too. You cannot assign a subtask independently — the assignee field on a subtask is disabled in the Task list. If the assignee on the main task is changed later, the new assignee replaces the previous assignee on every subtask.
Reassigning a main task is blocked once any of its subtasks has reached status Done. Complete the workflow, or wait until before any subtask is finished, to change the assignee.

Moving Main Tasks

Moving a main task to a different hub also moves every subtask to the same hub. The move operation can only be performed when:
  • The main task is Unassigned, and
  • Every subtask is also Unassigned.
Move task dialog

Move dialog showing the destination hub and the tasks that will be moved together

If the main task or any subtask is already Ongoing or Done, the move is rejected.

Editing Main Tasks and Subtasks

Editing a main task

The main task is fully editable in the Task list — title, custom fields, assignment, scheduling, and other Flow data can all be changed. Some changes on the main task are applied to every subtask automatically:
  • Assignee
  • Start time
  • End time
Other fields (such as customer name, order number, or other custom data) are saved only on the main task and do not affect the subtasks.

Editing a subtask

The assignee, start time, end time, and hub of a subtask cannot be changed on the subtask itself — these come from the main task. The subtask’s own data fields are filled in by the field worker while completing the task.
Action buttons like Assign, Unassign, Move, and Delete are disabled on subtask rows in the Task list. Use the main task to perform these actions instead.

Deleting Main Tasks and Subtasks

Deleting a main task

Deleting a main task deletes every subtask attached to it. Before the deletion is performed, the Task list shows a confirmation dialog that lists every task that will be removed so you can review the impact.
Delete confirmation

Confirmation dialog listing the main task and its subtasks that will be deleted together

Deletion is blocked if any subtask has already reached status Done. Completed subtasks must be preserved as part of the task history, so the main task cannot be deleted while any of its subtasks is Done.

Deleting a subtask on its own

  • A subtask that belongs to a Required Subflow cannot be deleted on its own — it can only be removed together with its main task.
  • A subtask from a non-Required Subflow can be deleted individually, as long as it is not already in status Done.

Frequently Asked Questions

Q: Can I assign a different user to a subtask? A: No. Subtasks always share the assignee of their main task. To change who works on the workflow, change the assignee on the main task — the new assignee will be applied to every subtask automatically. Q: Why are some action buttons disabled on a subtask row? A: Subtasks cannot be assigned, moved, scheduled, or (when they belong to a Required Subflow) deleted on their own. The Task list disables these actions on the subtask row because they are only valid on the main task. Q: What happens to the main task when I complete a subtask? A: The subtask’s status changes to Done but the main task remains in its current status until you mark it Done yourself. If the Subflow is Required, the main task cannot be marked Done until every Required Subflow has at least one completed subtask. Q: Can a subtask reference another Subflow inside it? A: No. A Flow that already contains a Subflow component cannot be selected as another Subflow’s target — Subflows are limited to one level. Q: I marked a subtask Done by accident. Can I delete it to start over? A: No. A subtask that has reached status Done cannot be deleted, and the main task cannot be deleted while any of its subtasks is Done. Completed subtasks are kept as part of the task history. Q: Can I move only one subtask to a different hub? A: No. Subtasks move with their main task. To move the whole workflow to another hub, both the main task and every subtask must be Unassigned, and the move runs against the main task.