Missing projects or entries
Successful login does not establish that the correct organization is selected. Confirm organization context before concluding that access is missing.
A plan exists but work has not started
For plugin-owned tasks, start or retry work through the application’s business entry. See Business tasks and execution sync for source ownership and synchronization issues. Creating tasks, entering dates and saving dependencies only update the plan. Ask the responsible Assistant to explicitly dispatch work and check for an execution record. If dispatch is rejected, check accepted predecessors, matching assignee and target, active group participants explicitly selected into the project, and external executor availability. External execution may also be waiting for an existing project attempt to end. Do not remove dependencies or mark work complete to conceal unmet prerequisites.Execution ended but no follow-up reply appeared
Open Execution history and distinguish runtime status from result-delivery status.
Reopening a conversation after disconnection can restore saved messages, but does not guarantee replay of every streamed fragment produced while offline.
Execution succeeded but acceptance fails
Check whether requirements changed, a newer implementation exists or the referenced file version changed. Old results or reviews cannot substitute for current evidence. If independent review was requested, the latest valid review must pass. Resolve failed, Changes required or Indeterminate results first. A review report itself still does not replace the final completion decision. Also confirm project editing rights and whether the task is managed by a business application with its own workflow.Execution failed or its outcome is unknown
Inspect that attempt’s error, captured output and retained files to establish what actually happened. After fixing model billing, authorization, connectors or executor problems, explicitly arrange a new attempt. Unknown status does not prove that execution never happened. Rerunning immediately can repeat file changes or external actions. Inspect the existing attempt first. Group errors provide an Assistant processing records entry for the corresponding attempt.Files are missing or cannot be downloaded
Check Outputs for formal delivery. A path in a reply may refer only to a working file. Determine whether delivery was requested, export failed or download permissions changed. Execution and file-export success must be checked separately. For working files, open Assets in the current project rather than using an old reference from another project or personal chat. See Shared files and deliverables.Dates, progress or views seem inconsistent
- No percentage: the executor or application has not provided explicit progress; use status.
- Planned and actual dates differ: one records expectations and the other actual execution.
- Tasks seem missing: clear search, status, assignee and kind filters and expand the task tree.
- Saving a plan reports a conflict: refresh and review other collaborators’ saved changes.
- Application tasks are stale: allow synchronization and refresh; verify the source operation succeeded and contact its maintainer if the issue persists.