PostHog / PostHog/posthog

Survey sent doesn't show relevant events

Open
#31,358 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug feature/surveys
Dominant language
Python
Stars
39.9k
Forks
3.4k
Avg merge
7h 27m
Merged PRs (30d)
222

Description

Bug Description

Please describe.
If this affects the front-end, screenshots would be of great help.

In short, the default Notification channel created for a survey contains an event filter "Survey Sent" - assuming this happens when a user clicks "Submit", it doesn't show relevant events. Here is a screenshot:

Image

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

  1. Create a new CSAT survey with default fields
  2. Save survey
  3. Add notification
  4. Connect to slack
  5. Inviate PostHog to private channel "X"
  6. Add private channel (X) as destination for Notification
  7. Save settings
  8. Submit survey
  9. See error

Additional Context

It looks like the available events change depending on survey type, and regardless "Survey sent" is never an option that appears in the matched events and actions.

Debug info
- [x] PostHog Cloud, Debug information: there is no valuable data here? im in the Us.
- [ ] 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]

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the CSAT survey notification flow described in the issue, including Slack delivery and the matched-events view. No files, tests, or entry points are named, so locate the survey event-filter and notification code first; done means the “Survey Sent” event is available and relevant events appear after submission.

Written by the indexing model from the issue text.

Assessment

Domain
analytics
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.