Log filtering with tags stalls after 50 results

Applies to:

Plan -
Deployment -

Summary

Issue: Filtering logs with tags = ["tag name"] stalls after 50 results and never paginates further. Cause: The equality operator (=) is not the correct syntax for tag filtering and causes pagination to break. Resolution: Use tags includes in the basic filter UI or tags in (...) in the SQL filter box.

Resolution steps

If using the basic filter UI

Use the includes operator

In the filter dropdown, select includes instead of typing an equality expression manually.

tags includes "review-needed"

Use `tags in (...)` with an exact value

Enter a filter clause only — do not use a full SELECT statement.

tags in ("review-needed")

If using the SQL sandbox to query directly

Replace the project ID and tag value as needed.

select id, tags
from project_logs('<your-project-id>')
where tags in ("review-needed")
AND created >= NOW() - INTERVAL 7 day
LIMIT 100

Note: Entering select * from project_logs(...) into the SQL filter box (not the sandbox) produces a parse error. The filter box accepts filter clauses only. In the SQL sandbox omitting created >= can cause query timeouts. Adjust the interval as needed (7 day, 30 day, etc.).

⌘I

All troubleshooting guides

Log filtering with tags stalls after 50 results

Summary

Resolution steps

If using the basic filter UI

Use the includes operator

If using the SQL filter box

Use `tags in (...)` with an exact value

If using the SQL sandbox to query directly

​Summary

​Resolution steps

​If using the basic filter UI

​Use the includes operator

​If using the SQL filter box

​Use tags in (...) with an exact value

​If using the SQL sandbox to query directly

Summary

Resolution steps

If using the basic filter UI

Use the includes operator

If using the SQL filter box

Use `tags in (...)` with an exact value

If using the SQL sandbox to query directly