# Check results and troubleshoot

Validate the saved rule, trigger, agent execution, and business result separately. The overall task is incomplete until all relevant steps are confirmed.

## Four checks

1. **Rule saved:** it exists in the list and reopened configuration is correct.
2. **Trigger received:** the scheduled time, API call, or delivered event produced the corresponding run record.
3. **Execution produced a result:** open history or the conversation to inspect model and tool execution and errors.
4. **Business outcome matches the goal:** verify summary sources, generated files, or actual changes in the external system.

For messages or email, also verify the recipient and actual delivery. A connection test is not a delivery check.

## Common problems

| Symptom | Check |
| --- | --- |
| Submission keeps loading | Search the list for the name before deciding whether to retry |
| A paused task did not run | Whether it needs enabling and whether the new status was saved |
| No record at the expected time | Schedule preview, next trigger, date, and filters |
| API responds but no business result | Corresponding run and final state, not only HTTP status |
| Event did not trigger execution | Source subscription, delivery record, authentication/signature configuration, and target rule |
| Material missing during execution | Knowledge bases and tools available at run time; avoid temporary-attachment dependencies |
| Tool failed | Credentials, permissions, network, and then the actual call content |

For further diagnosis, retain the rule name, trigger time, conversation or run entry, and original error for the maintainer.