Fix Task Builder workflows

Use this page when a Task Builder Session is missing, cannot be edited, or is not ready to publish. Task Builder changes draft work through the local AI conversation and CLI; publication remains your action in the application.

Ask your local AI tool to inspect the Task Builder Sessions available to the initialized project.

Ask your local AI tool to include archived sessions when needed, select an available Building session, or clear an outdated local selection before choosing the right one.

The expected result is a current Building session selected for later draft changes. If the session is unavailable, confirm the selected repository project and your access without attempting to infer another project's sessions.

Published sessions are immutable history. Return to the planning conversation and create or select a Building session for new draft work. Do not try to alter a Published session or its published records through Task Builder.

The expected result is a Building session where draft changes are available. Published tasks and Plans use their normal product workflows after publication.

Read every readiness message before publishing. Errors prevent publication and must be corrected in the planning conversation or its CLI mutations. Common causes include missing required content, out-of-range Mass, unavailable or conflicting labels, invalid draft membership, and dependency references that cannot be published safely.

Warnings do not block publication. An archived Building session can be ready, but its published history remains hidden from normal discovery until it is restored.

The expected result is no readiness errors and an intentional decision about any warning before you use the visible Publish action.

Use the stable draft IDs shown by session output to inspect the reported drafts. Remove the circular dependency so no draft eventually depends on itself. For labels, choose only labels currently available to the selected project and avoid conflicting labels in the same scoped group.

The expected result is a readiness result without that error. Do not replace a label or dependency blindly: confirm that the revised draft still represents the intended work.

Ask your local AI tool to refresh the session and use the stable draftPlanId or draftId from the current result. Do not substitute a Plan or task position. Both IDs must belong to the same Building session when assigning a task to a proposed Plan.

If a grouping should be cleared, ask the local AI tool to return the draft to Standalone; it does not change published Plans or tasks. If a Plan was removed, its former member tasks already became Standalone and keep their stable task IDs.

The expected result is an assignment to one current same-session proposed Plan or an explicit Standalone task, without changing published Plans or tasks.

Publication is all-or-nothing. If it fails, no partial set of Plans or tasks was created and the session remains Building; resolve the reported readiness problem and publish again when ready. If a session or its published history is hidden, use the archived view and restore it through the application when that visibility is wanted.

The expected result is a Published session with its complete set of published records, or a still-Building session with an actionable error.

For the product language used by Task Builder, see alterac.ai terminology. For repository or sign-in problems before session commands run, see Fix repository setup.