Bug report: Error saving default columns on events in data management
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Bug Description
Please describe.
When editing default columns for matching events on an event definition in data management, if you check the box for Save as default columns for this event type , error toast pops showing "Failed to save columns to event definition".
The console shows a 402 payment required error, with message detail "This feature is part of the premium PostHog offering. To use it, subscribe to PostHog Cloud with a generous free tier."
The customer reporting the bug is on the YC plan, and the Save as default columns for this event type does work for them on the Activity page.
How to reproduce
Example event definition in data management
- Go to Data management --> Event definitions and click on an event
- Scroll down to the
Matching eventssection o' the page - Click the
Configure columnsbutton - Add a property (e.g., one which exists on the event)
- Check the box for
Save as default columns for this event type - Click the
Savebutton - See the error message
Additional context
From: https://posthoghelp.zendesk.com/agent/tickets/37500 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/38628)
Debug info
Debug info
Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/01992ba9-9deb-7f5f-ac36-783abd46b8fd?t=1271
Admin: http://go/adminOrgUS/019819c9-3651-0000-d12e-e576fac3858e (project ID 195693)
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure from the event definition's Matching events section using Configure columns, then compare it with the working Activity page flow. Trace the save request and its entitlement handling for the YC plan; done means default columns save successfully without the 402 error and existing behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100