Prerequisites
- A Cogno workspace where you can create or edit Tasks.
- For agent work, an Environment connected to the Task’s Project. See Set up a Project.
Open a Task
Each full Task has its own page and shareable link. Back returns to the page where you opened it; Forward reopens it. Sidebar links leave the Task in one click. Moving between pages preserves your working sessions. In a browser, selecting a Task opens a side peek over the current page. Drag its left edge to resize it; release to save the width, or press Escape while dragging to cancel. You can also focus the edge and use the left and right arrow keys to adjust the width. Use Expand to full view to open the full Task or Close task panel to return to the list.
Shared HTTPS Task links prefer the Cogno desktop app on your device. Supported
Desktop releases open verified links directly; other installations use a short
browser handoff. If the app cannot open, the link continues in Web automatically.
You do not need to choose between the app and the browser.
Exact Task links from other apps open only in the quick peek by default, leaving
the main Cogno window where it is. Project, Meeting, Inbox, and Task sub-page links
continue to open in the main window.
The same goes for Tasks you open inside the desktop app’s main window: a Task link
in a description or in the conversation, a Task link card, and a Task chosen in the
list, board, calendar, Gantt, Project, or Inbox open in the quick peek, and the
main window stays on what you were doing. Hold ⌘ (macOS) or Ctrl (Windows)
while you click to open the Task in the main window instead. Tasks in the sidebar
and a Task you just created open in the main window.
If you are signed out in Desktop or your session has expired, the quick peek hands
the link to the main window for sign-in. Cogno returns to the same Task after
authentication. The link does not grant access: your account must have permission
to view that Task.
To open every Task link in the main window instead, turn off Open Task links in a
quick peek in Settings → Preferences. The preference applies to the desktop
app on macOS and Windows and saves automatically.
Inside a quick peek, select Description, Conversation, or Changes & PR to open that part of the Task in the main window without closing the peek. Cogno links and link cards in the description open their destination in the main window. The Project chip lists the Workspace’s active Projects with the Task’s current one checked: choose another to move the Task there, or choose Open Project to open it in the main window. While the peek shows the Task of a meeting you are recording, choosing a Project moves that meeting and its Task. External links open in your browser. Select Open in Cogno to expand the Task into the main window and close the peek.
The desktop quick peek updates the open Task’s title, status, assignee,
description, and run state automatically as they change. It also refreshes when
you reopen it or open another Task in it. This applies on macOS and Windows.
Review a description from quick peek
The browser and fallback quick peek use the full description review controls. Select text in the description, choose Comment, write the change you want, and choose Add. Existing comments remain attached to their quoted passages in the description. On macOS 26, the native quick peek keeps the description read-only but lets members with permission to edit content select text and add a review comment. Members without that permission do not see Comment. Existing review comments appear as a count below the native quick peek description. Choose Open in Cogno to open the Task’s description and its review comments. For a Cloud Project, the full Task view hides the conversation pane and its message composer. Task properties, description, and delivery remain available. Local Projects keep their conversation pane. Reloading the desktop app preserves your pane arrangement, right-panel visibility, and each Task’s expanded or folded terminal. While content loads, the work surface uses your saved arrangement. The address determines which Task opens. The top-right side-panel button appears only when the current Task surface has an available side-by-side split. It folds the right side of that split, which can contain the conversation if you swapped the panes. A fully stacked arrangement has no side-panel button. Your saved visibility preference is kept when the button is unavailable and applies again when you return to a foldable arrangement. In the desktop work surface, drag a boundary between panes to resize them. Release to save the layout, or press Escape during the drag to restore it. A Task bound to another machine shows Runs on <machine> or Runs on another machine. You can still read and edit the statement from the current surface.Understand Cogno-managed work
A Task filed for someone else, such as a commitment from a meeting, stays Ready until someone starts it. Opening one that has not started shows its description with a message box below, the same as a Task running on a teammate’s machine. Sending a message starts it for its assignee on any member’s machine that has a folder for the Project; the assignee does not change, and you do not need to assign it to yourself first. Files can be attached once it is running. In execution notices, an unavailable display name appears as the assignee. Cogno can create and start Tasks from connected events. It creates them directly in In Progress. Its Tasks sit among everyone else’s, in the same order and with the same look and actions; there is no separate Cogno group or colour. Hovering a sidebar Task shows Cogno’s mark when Cogno filed it.- Top-level Tasks keep the source they came from. Show the Source column or read the inline from <source> mark.
suggested:true to see Tasks
whose proposed status remains unresolved. See
Task statuses.
Create a Task
Dictate a request on Desktop
Use the microphone in the + Task composer to speak your request. On first use, select Set up dictation to download the local model (about 190 MB). The download shows its percentage. Recent Desktop versions offer Pause download and resume from the saved bytes when you select Set up dictation again. Select Dictate and speak. The microphone turns into a round stop button in the same place, and a small pill opens beside it with a live waveform and the elapsed time; the composer’s other controls fade until you finish. Select the same button, Stop and transcribe (or press Return), to transcribe, or select Cancel recording in the pill (or press Esc) to discard the recording. While the words are on their way, the pill shows Transcribing…. The returned text is appended to your current draft, including edits made while transcription was pending. Create Task and Later come back once recording and transcription finish. Closing the composer cancels a recording it started. Recent Desktop versions use the current Workspace’s Project and member names as local spelling hints. The hint list is bounded and belongs to that recording; there is no custom glossary editor yet. Older Desktop versions continue to transcribe without those hints. Recognition improvements have not been measured. Audio stays on your device for this flow. After the model is installed, dictation works offline. In browser quick creation, the local dictation control is unavailable.Create and start with a connected Engine
For a Task assigned to you, select a Project and open Run on. Choose your configured Cloud or Local Environment, or leave Automatic selected. Only your Project Environments are offered; unavailable Environments cannot be selected. The selected Environment is saved before the first message starts. If it becomes unavailable, Cogno reports the failure without choosing another machine. Later saves the Task and its selected Environment without starting. Desktop and browsers with an available Engine use the same prompt-first composer. Attach files and select Create Task to open the Task and send its first message through Engine. When model discovery is unavailable, Engine uses its default executor and model. Browsers without an available Engine use the full form below. Select Later beside Create Task to save the request to the backlog without starting a run. Select Work and write in What should Cogno do? Choose a Project, base branch, and model for Local execution, then select Create Task or press Enter. For Local execution, Cogno creates a Ready Task, opens it, and sends the prompt as the first turn. If creation fails, your prompt and attachments stay in the open composer. You can edit the prompt, Project, or model and select Create Task again; each attempt uses the current input. A previous unfinished creation does not block a new one, and reopening the composer does not restore that previous request. If the Task was saved but its response was lost, an automatic or manual retry can create a duplicate Task. If saving the first input on your device fails after the Task is created, that Task can remain without starting its first turn. For Local execution, the person chip beside the Project (Assignee) names whose machine runs the work. It starts as you. Choose someone else and Create Task assigns the Task to them and queues a run for their machine instead of opening it here: the run starts at once when they have a folder connected for the Project, and otherwise the Task waits under their tab in In Progress until they connect one. The attachment, model, and base branch controls belong to your own machine, so they step out of the composer for someone else. The + on a person’s tab in In Progress opens this composer preset to that person. For your own Local or Cloud execution, you can attach or paste files before creating. One message accepts up to 20 files, each up to 25 MiB. The send waits until every attachment finishes loading. Cloud uploads files in small pieces at their original quality before sending the message. If sending fails, retry from the restored composer. A remote computer running an older Engine may require an update before it can accept attachments. The base branch defaults to the repository default. A direct Environment has no Git branch or automatic pull request. A named local-only branch also shows no automatic PR.Titles from your request
The composer has no title field. The Task is titled with the first line of your request, cut at 60 characters. While Readable Task titles is on in Settings → General (it is on by default), Cogno then replaces that title with a short one that says what the Task is for, in the workspace language. If Cogno cannot name it, the first line stays. A title you type in the full form is never renamed, and once you edit a title yourself Cogno leaves it alone. Turn Readable Task titles off to keep the first line as the title. Changing it needs permission to edit workspace settings.Choose an exit from the full form
The full form’s How to proceed panel combines assignee, Environment, and the next action:1
Describe the work
Add a title and description. The editor accepts rich text, mentions,
tables, and images.
2
Choose who and where
For a Local Project, the Environment starts at Automatic when a machine
can be selected. Open it to use Automatic routing or choose a registered
Environment. A Cloud Project uses its Cloud environment for any assignee.
3
Choose what happens next
- Watch it get built creates the Task and starts implementation.
- Plan it first creates the Task and starts a planning turn.
- Later creates the Task in Backlog without a run.
- Create creates the Task in Ready without a run.
Start and follow work
There is no separate run button. In the desktop app, send a message in the Task conversation. The first message claims an Environment and moves the Task to In Progress. Later messages continue the same Task session. The composer reads Message the agent… and sends to the Task’s connected Engine session. If this surface cannot reach the machine, it shows the Task’s location instead of offering a message box. While work starts, the conversation shows Starting…. During the turn it shows Running…, and the send control becomes Stop. Enter on another message adds it to the queue for the next turn; ⌘Enter sends the composer text and the queue into the running turn now. Stop the turn before changing its model. A sent message leaves the composer at once and appears in the conversation; the send button stays disabled until Engine accepts it. If the send is refused, the text and attachments return to the composer so you can send again. Once a message is queued, it appears above the composer. The current turn continues while the message waits. Use Send now, Edit, or Remove from queue on that message to change what happens next. Cmd/Ctrl+Enter sends the queued messages into the running turn. If the provider is still connecting, the send stays in progress while it becomes ready. If the send fails, the queued messages remain available for retry. Use Close on a send error notice to dismiss the notice; your draft remains. Attach, drop, or paste files into the composer. Images appear as thumbnails that open full size. Failed uploads block the message until you remove them. After you request a send in Desktop, opening another Workspace or Task allows the first message and a message waiting for a folder move to continue delivery. Keep the app open until Engine accepts the message. Accepted work continues independently of the Workspace you are viewing. If delivery fails, open that Task to review the restored text and attachments and retry.AI choice for background work
With an up-to-date Engine, starting a new Task conversation or manually switching its AI also chooses the conversation for later background work on the same connected Environment. A newer background conversation does not replace that choice. Replies explicitly addressed to an older conversation still use that conversation and its original AI and billing. If the chosen conversation is closed or no longer usable, the queued work fails with a message asking you to open the Task and choose an AI in a new conversation. Cogno does not silently switch to another provider. A replacement conversation that is still starting is allowed to finish starting before waiting work is assessed.Replies in the source conversation
For a Task created from Slack, Microsoft Teams, or Discord, a completed run that was answering that conversation can finish before it calls a message Tool. While Cogno keeps the Task In Progress, it schedules one follow-up to read the Task and source conversation and report what happened. If another run is active, this check waits until that run ends, including when it fails. Several waiting completions share one follow-up. Messages sent by another run do not cancel this check. Cogno checks the source conversation even if that run posts elsewhere or sent its message before a new request arrived. The follow-up reads the existing conversation before replying and sends nothing if the answer is already there. It starts no new work, and its own completion never creates another automatic follow-up. Replies still require the Project’s current integration permissions and consent to send messages. Moving the Task out of Cogno-managed work keeps your control and prevents this recovery from restarting it.Start work for a person from the list
Drag a Task onto a person’s tab in In Progress, or onto the rows under the open tab. The Task is assigned to that person and a run is queued for their machine. On a Project page, dropping a Task onto your own name at the top of the sidebar does the same for you.- With a folder connected for the Project, the run starts right away.
- Without one, the row shows a hollow branch mark whose tooltip reads Starts when <name> connects a folder. The run starts on its own the moment they connect one.
- A Task that already runs in an environment stays with its owner. While you hold it over another person, the lane shows Fixed to <name>‘s environment, and releasing it changes nothing.
- While a run is executing, the row’s mark spins for everyone in the workspace, not only on the machine doing the work.
Move through the lifecycle
Change status from the Task, its row menu, or by dragging in List or Board.- Moving into In Progress without starting work is refused with Send a message in the Task to start work. Dropping the Task on a person’s tab in In Progress is the way to start work from the list; see Start work for a person from the list.
- Moving out of In Progress during a live run opens Stop the running agent and move? Select Stop and move to retain partial results and end the run.
- A completed run can propose Backlog, Ready, or In Review. Applying that proposal releases Cogno control. A failed or stopped run leaves the Task in In Progress.
- A clear reply in the Task conversation can decide the state directly. An explicit acceptance moves the Task to Done; a request to defer moves it to Ready or Backlog; a request for review moves it to In Review; and a cancellation moves it to Rejected. If the meaning is uncertain, the agent asks or reports before moving the Task.
- Select Done when the work is complete.
Edit, archive, or delete
The Task statement contains Status, tags, dates, assignees, Project, preview, and actions. Descriptions support rich text, collaborative editing, and version history. Text, Office, and other files in a description appear as compact cards with their filename, file type, and available size. Select the filename to open the file, or use its More menu to open or download it. Images, videos, and PDFs keep their inline previews. Diagrams and embedded pages load as you scroll near them. Diagrams and embedded pages you have not interacted with can be released when far away, and load again when you return. After you enter or interact with an embedded page, it stays loaded while that description is open so its form or playback state is kept. Add Parent task from the row’s... menu to nest the Task under a
top-level Task, move it to another parent, or clear it with No parent. A
Task that has sub-Tasks of its own cannot become a sub-Task.
Archive removes a Task from active views and is reversible. Delete
permanently removes the Task, sub-Tasks, comments, attachments, and history.
On a machine that ran it, deletion also removes the local conversation and
working copy, including uncommitted changes.
Close a Task that has sub-Tasks
Moving a Task to Done, Rejected, or Archived moves its open sub-Tasks there with it, and cancels any unfinished agent work on them. A sub-Task that was already archived stays archived. Reopening a parent — Backlog, Ready, In Review — leaves its sub-Tasks where they are. When the Task still has open sub-Tasks, Cogno asks first and names how many the move closes. Choose Close all to go ahead, or Cancel to leave everything where it is. For ten minutes after the move, Undo on the toast takes the whole press back: the parent and every sub-Task the move closed return to the status each had. A sub-Task you changed yourself after the move stays where you put it. The undo does not restart a run the move cancelled — the Task comes back, and you start the run again if you want it. You can also press ⌘+Z (Ctrl+Z on Windows and Linux) to take back your latest status change in the workspace — Done, Rejected, Archived, or any other move except into In Progress. Press it again to take back the one before. An archive of several selected Tasks comes back as one. While you are typing in a text field or a dialog is open, the key undoes your typing instead.A sub-Task belongs to its parent’s Project. Moving a Task to another Project
moves its sub-Tasks with it, and filing a Task under a parent in another
Project moves it into that Project.
Tasks that need attention
Task rows show a cloud icon to the right of the title when the Task’s bound machine is a Cloud machine. The icon remains visible while the Task runs or has unread activity, and also appears beside the title in its hover card. Hover over the icon to read the machine name. A remote computer connected through SSH keeps its computer mark; being remote does not make it Cloud. The list and Gantt highlight open Tasks whose latest run failed or whose running agent is waiting for approval. Hover to read the reason. In the list, a parent also has a subtle highlight when a sub-task needs attention. Completed, archived, and rejected Tasks are excluded. A failed run superseded by a direct execution is excluded. Time since the last update alone does not produce a highlight.Troubleshooting
For other failures, see Troubleshooting.
Related docs
Moving around the desktop
Inbox, Meetings, and All Tasks stay at the top of the sidebar. Saved views appear before Projects. Click a Project name to open its page. Clicking the current Project again expands or collapses its working Tasks; its disclosure arrow does the same. Select the filter button beside Projects to choose which Projects appear. The sidebar keeps every Project in place and replaces each row’s actions with a switch. Turn switches off or on, then select the filter button again to finish. Hidden Projects collect in Hidden projects at the bottom of the sidebar; select it to open or close the list, open a Project from there, or select the eye button to show it again. This changes only your sidebar; it does not archive or alter a Project. The choice is saved to your account, so desktop, web and the mobile app hide the same Projects. In the mobile app, press and hold a Project and choose Hide or Show from its menu.Pin Tasks in your sidebar
Right-click a sidebar Task and select Pin Task to move it to the top of its Project. Select Unpin Task to remove the pin. Pinned Tasks stay at the top in the order you drag them into. The other Tasks under a Project are listed by the last time someone sent the Task a message, newest first; a Task nobody has written to yet is placed by when it was created. A run starting or finishing does not move a Task. Pins belong to your account and affect only the sidebar. Task order in List, Board, Calendar, and Gantt is unchanged.Use the sidebar keyboard controls
Press Tab or Shift+Tab to focus a Project or Task, then Enter to open it. Press Command+1–9 to open the corresponding visible sidebar Task, including from the Task list screen or its search field. You do not need to focus the sidebar or hold Command first. Folded Task rows are skipped.
Status and archive actions require permission to edit the Task.
To finish a Task without moving to its Done button, hover its sidebar row or its hover card and press D. A focused control takes priority over hover. The D shortcut stays inactive while you type, use an IME, hold a key, or have a dialog or menu open, and while the change is saving. It uses the same child-Task confirmation and undo history as the existing Done action.
Hover the same row or card and press A to open the Archive confirmation, or P to toggle Pin Task / Unpin Task. These shortcuts use the same actions and permissions as the right-click menu. The same typing, IME, held-key, overlay, and focus guards apply; D and A also wait while a Task update is saving.
P, D, and A also work while that sidebar Task’s right-click menu is open.
They do not trigger while you type in a menu field.
Back and Forward remain available in the title bar when the sidebar is collapsed. Settings has a separate Return to work action.
The Task list address retains its applied search, filters, sort, and layout. Back and Forward restore that entry. A bare workspace entrance reopens the last work page remembered in this window for your account and workspace; explicit links always take precedence.
In Board view, hiding or showing a status column updates the same status filter in the address. Reload and history therefore restore those columns too.
Tasks on mobile
Ignore a question on mobile
For a text-input or choice card on Home, swipe left or select Ignore beside Hold to dismiss it without answering. Undo is available for three seconds. Ignoring tells Cogno that you declined the request; it does not choose an answer or grant permission. Hold keeps the request for later instead. If sending fails, the card returns with an error so you can retry. For an existing Ready Task with no execution environment, open Chat and choose an available Project environment. The list shows each machine and environment name. Selecting one prepares the Task and opens the message composer; send your first message to start the conversation. If no environment is available, open Cogno on your machine, check the Project execution settings, and retry. When a Task offers both Detail and Chat, swipe left from Detail to open Chat. In Chat, swipe right from the left third of the screen to open the Task list; swipe right from the rest of the screen to return to Detail. The selected tab indicator follows your finger while switching views and settles when you release it. A short, cancelled swipe returns the indicator to the current tab. The list initially shows your Backlog, Ready, In Progress and In Review Tasks. The filter button indicates when the list is restricted, including to your own Tasks. Open it to check the assignee and status choices. Matching Tasks are loaded beyond the first 200 results. Pull to refresh, or return to the list from a Task, search or another tab, to fetch the latest state. Sidebar search has its own filters. It initially searches everyone’s Backlog, Ready, In Progress and In Review Tasks. Open the filter button beside the search field, then Status → All statuses to include Done, Archived and Rejected. You can also select individual statuses or restrict the assignee. Search filters do not change your sidebar list filters and reset when you close search. Task creation accepts up to 20 photos or files, each up to 25 MiB. You can take a new photo, choose existing photos, or add files. A camera or picker error leaves the current input intact. On mobile, Task creation and chat share model, effort and access controls with Desktop. Model and effort choices apply to the next message. After that turn starts, other devices show the Session’s latest settings unless you have explicitly chosen settings for an unsent message there. A refused send keeps your selected model and effort for retry. On Engines supporting Session access updates, an access change is saved to the existing Session immediately and appears on Desktop too. For an attended conversation, a change that cannot apply live interrupts the current turn and continues the same conversation with the new access. Read-only and autonomous work keep their existing constraints. Older Engines keep existing Session access choices disabled. A refused change shows an error. Full access remains limited by the machine’s configured ceiling. See Change access while the agent works. The mobile Diff opens the Task’s working changes using Engine’s default base. Use Compare from and Compare to to compare branches instead. Retry a failed summary or file patch from the error shown there. Touch and hold a sidebar Task to open its actions. Choose Pin Task or Unpin Task to change its personal sidebar pin, or open Status to choose a new status. Archive and Delete appear directly in the menu; Delete is marked as destructive and asks for confirmation. Before moving a Task to Done, Archived, or Rejected, the app asks you to confirm that its subtasks will close and their runs will stop. To move a Task to In Progress, start work from the Task. Keep holding and drag up or down to reorder Tasks that share the same status, parent, and Cogno-managed state. On iOS, a parent Task’s subtasks move with it. The order is saved including Tasks hidden by filters. Reordering Tasks is supported in Projects with 200 Tasks or fewer. To reorder Projects on iOS, touch and hold the Project name and choose Move up or Move down. On Android, touch and hold the Project name, drag it up or down, and release. The order is saved to your account. In the Tasks filter, open Status to select several statuses in a row. The menu stays open and updates the selection; tap outside it to close.Comment on text on mobile
On iOS, touch and hold text in Detail or Chat, then drag the selection handles to choose the passage. Select Comment in the text-selection menu to quote it. The menu also keeps the system’s copy, select-all, lookup, translation, search and sharing actions when iOS makes them available. On Android or an app without the native selection menu, touch and hold text to use the system selection actions. Use the separate Comment button beside a passage to quote the whole passage. Queued messages show their review comments as quotes and readable text. When editing a queued message, edit the message and each comment in separate fields; the quoted passages and comment authors stay attached. Write what should change and select Add. Pending comments appear above the chat input, where you can edit or delete your comments before sending them. Select Send review (count) to send the pending comments together to the agent, or send your next chat message to include them with it. Description comments are shared with Desktop. Unsent chat comments stay on the current device.View images on mobile
Tap an image in the Task description or chat to open it full-screen, like a Mermaid diagram. Select Close to return. Loaded images are cached on the device and reused when you return to the description or chat. If an attachment image fails to load, Cogno refreshes its temporary preview link once.Review Task activity on mobile
Open a Task’s Detail, then select Activity to see its Task-scoped changes newest first. Each entry names the member who made the change and when it happened. This history covers Task changes; it is not a record of every action Cogno performs in external services. Undo appears only for your latest status change while it may still be restored. Cogno asks the server again when you select it. If another change or the time limit makes the action unavailable, the entry shows Undo unavailable and does not report a successful undo. The screen shows an undo action only on the eligible entry. Other history rows show the change, member, and time.Create a Task on mobile
Use Run on to choose one of your Project’s connected folders, labeled Cloud or Local with its machine name. Automatic selects a destination only when exactly one of your Project’s connected folders is eligible, and shows that machine below the form. If several are eligible, choose one explicitly before creating the Task. It does not classify the Task’s content. To require Cloud execution, select the Cloud destination explicitly. If an explicit destination is unavailable, Create & Run stays disabled instead of switching to another machine. The row above the input fields shows access, model, and effort on the left. For a Project configured to create a worktree, the right side shows the configured base branch, such asstg. Tap the branch name to choose another Engine-provided
branch in a searchable menu with the same presentation as model selection.
The selection applies to the first Session; leaving it unchanged uses the Project’s
configured base branch. The comparison base and target for reviewing changes remain in Diff.
When the Project is configured without a worktree, the right side shows In this folder.
The run starts directly in the configured folder without creating a separate worktree;
there is no starting-branch selection.
Tap the + beside a Project to create a Task. Closing the creation sheet keeps
the title, description, and attachment references on this device for that
account, Workspace, and Project until you submit it. Select Close
to pause, then open creation for the same Project to resume the title, description,
and attachments. Changing Projects shows that Project’s own draft.
Submitting saves a separate local delivery request and clears the editing draft.
Unsubmitted drafts are not saved to the server.
Enter Title and What should be done, then choose a Project. Select Add attachment, then Take Photo, Add Photo, or
Add File. Take Photo asks for camera access and offers to open system settings when access is refused.
Select Create & Run to save the Task, add the attachments to its
description, and start the work. This action is available when the Project has an
eligible machine connection. Model discovery does not block creation; when no
model is selected, Engine uses its default executor and model.
Choose a model above the title and description fields. Open the model menu and
select Refresh models to read the choices again without losing your title,
description, or attachments. If the connection could not be loaded, the model row
stays visible with Retry.
After the app saves the submission and copies its attachments on this device,
the sheet closes. You can continue using the app while it creates the Task,
uploads attachments, and requests execution. The submission status stays visible
on the main screen. The Task enters In Progress when execution is accepted;
saving the submission alone does not mean the run has started.
Leaving the app pauses unfinished delivery. Returning resumes it, including after
an app restart. If creation, an attachment, or execution fails, retry the saved
submission from the main screen. The app retains the input and copied files and
reuses the same Task when one has already been created. The run starts only after
all attachments succeed. An execution failure does not delete the saved Task.