You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Realised thanks to #21528 - that our responses count endpoint for surveys list queries data from all time which can be pretty slow on big teams. This should instead use the earliest created date, like in the PR above to query responses count.
Please describe. If this affects the front-end, screenshots would be of great help.
If you are on PostHog Cloud it would be really valuable if you can share any links where the problem occurs. This speeds up our ability to troubleshoot tremendously.
How to reproduce
Additional context
Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]
- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]
- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]
The text was updated successfully, but these errors were encountered:
… in a team (#22011)
Resolves#21775
This PR addresses an issue with how we calculate response counts for a given survey in the surveys UI.
Instead of filtering out all events for a team by the event name of survey sent, we will look at only those events that are created after the team created their first survey. This should be a good indicator for when we should start to see survey responses for a given team.
Bug Description
Bug description
Realised thanks to #21528 - that our responses count endpoint for surveys list queries data from all time which can be pretty slow on big teams. This should instead use the earliest created date, like in the PR above to query responses count.
Please describe.
If this affects the front-end, screenshots would be of great help.
If you are on PostHog Cloud it would be really valuable if you can share any links where the problem occurs. This speeds up our ability to troubleshoot tremendously.
How to reproduce
Additional context
Debug info
The text was updated successfully, but these errors were encountered: