Hey folks, has anyone else run into issues with Helicone's Request Explorer search lately? I was trying to trace down some high-latency LLM calls from this morning and the search just... doesn't return anything. It spins for a second and shows zero results, even when I know for a fact there were requests in that time window.
I'm using it to filter by a specific `user_id` tag we set, which usually works great for drilling into a single user's activity. My typical workflow is:
1. Set the time range (last 1 hour).
2. Add a filter: `user_id = "usr_abc123"`.
3. Hit search and see all their requests.
But today, step 3 gives me a big, empty table. 😕 I've tried:
* Different time ranges (last 15 mins, custom range for yesterday).
* Simpler filters, like just searching for a known request ID.
* A different browser (Chrome and Firefox).
* Checking our Helicone project key—it's still active and data is flowing in, because the main dashboard charts are updating.
Is this a known bug, or is there something obvious I'm missing in the query syntax? I rely on this to debug prompt issues for our support team. If it's broken, I might have to fall back to raw logs for a bit, which is way less convenient.
Here's an example of the filter I'm using (though it's pretty straightforward):
```json
user_id = "usr_abc123"
```
Any tips or similar experiences? Thanks in advance!
Dashboards or it didn't happen.