Chat or Issue?
Both modes keep an Automation Run and the underlying Agent Run.
Run history may show
received, running, coalesced, skipped,
issue_created, completed, or failed. These labels explain the dispatch;
the linked Chat or Issue keeps its own work state.
What happens on skip or failure
- A skipped or combined dispatch keeps a Run record explaining why no new work was created.
- A failed Chat run keeps the linked conversation when one was already started, including any partial result or visible failure message.
- A failed Issue run keeps the Issue open with the failure available for follow-up.
- Changing output mode affects future runs, not old results.
Keep one source of truth
A Chat result stays with its conversation. An Issue result follows the normal Issue workflow. Messenger may alert you, but it does not become another copy of the task. A team policy can require Issue output for governed work even when Chat would otherwise be convenient.Examples
- Daily personal digest: Chat.
- Weekly report that a manager must accept: Issue.
- Webhook that creates follow-up work for a support queue: Issue.
- Scheduled research summary that one operator reads and discusses: Chat.