Troubleshooting
Missing logs
A run shows in the dashboard but its log lines cannot be found in search — retention, storage quota, and query tips.
Most common causes
| Cause | Check |
|---|---|
| Run predates the connection | Logs are not backfilled — only runs that started after you connected have searchable logs |
| Retention window passed | Logs older than your plan's retention are removed — plans |
| Storage quota exhausted | Settings → Usage shows indexed volume vs your plan's storage limit |
| GitHub never produced the log | Jobs cancelled before starting, or GitHub-side log upload failures, have no log to index |
| Query does not match | Search is substring-based — see below |
Search tips
- Minimum 3 characters; shorter queries are rejected.
- Terms are AND-ed —
docker pushrequires lines containing both words. Remove terms to widen. - Wrap a phrase in quotes to keep it together:
"Connection reset by peer". - Search is case-insensitive substring matching — not regex.
*is treated literally. - Check the facet filters — a selected repository or conclusion filter silently narrows results.
- Check the time range — logs outside the window are not searched.
If a recent run has no logs at all
Log download happens after the job completes; wait a minute and refresh. Still empty after a few minutes? Contact support with the repository and run ID.