Test and Troubleshoot Tasks
Test tasks before relying on them for recurring work.
Run a private test from the editor
Section titled “Run a private test from the editor”Open the task in a channel, then select Test task. This runs the task in a private thread in that channel, visible only to you. The thread is labeled with the task name and links back to the task editor so you can adjust the instructions after reviewing the response.
Private editor tests do not wait for a real schedule, webhook, Slack event, or RSS item. Use them to validate instructions and teammate behavior before relying on live trigger events.
Test checklist
Section titled “Test checklist”- Confirm the teammate has the connectors it needs.
- Send or wait for a representative trigger event.
- Open the generated thread.
- Inspect the teammate’s response and tool calls.
- Tune the task instructions.
- Confirm the right people are notified.
Common issues
Section titled “Common issues”| Issue | What to check |
|---|---|
| No thread was created | Trigger setup, webhook URL, app permissions, schedule timing. |
| Teammate cannot access data | Connector scope, teammate connection assignment, expired credentials. |
| Output is too broad | Narrow the trigger or add clearer instructions. |
| Too many notifications | Tune teammate notification settings or task instructions. |
Keep a feedback thread
Section titled “Keep a feedback thread”When a task produces a weak result, fix the instructions close to the example. The best task instructions usually come from real event payloads and real review feedback.