Tool execution logs
Execution logs record every tool run triggered by assistants — parameters sent, HTTP status, duration, errors, and transform outcomes. Use them to debug production issues without exposing secrets to visitors.
View logs
Section titled “View logs”- Go to Tools → select a tool → Logs.
- Filter by time range, status (success/failure), or deployment.
- Open a row for request summary, response size, and error detail.
Org-wide activity may also appear in the dashboard audit feed.
Log fields
Section titled “Log fields”| Field | Description |
|---|---|
| Timestamp | When the run started |
| Assistant / deployment | Which surface triggered the call |
| Parameters | Path, query, body values (secrets redacted) |
| HTTP status | Upstream response code |
| Duration | Round-trip latency |
| Error | Validation failure, timeout, or API message |
| Rich content | Whether transform produced cards |
Common patterns
Section titled “Common patterns”| Pattern | Likely cause |
|---|---|
| Spike in 401 | Expired OAuth or rotated API key |
| Strict validation errors | Model supplying wrong types — tune descriptions |
| 200 but no cards | items_path mismatch |
| Timeouts | Slow API — async mode + notifications |
Retention
Section titled “Retention”Log retention depends on your plan. Export via Tools API for longer archival if needed.
Privacy
Section titled “Privacy”Credentials and raw auth headers are never stored in logs. Parameter values may be truncated per data handling settings.