Bug report: error on saving default event table columns
Open
Nobody has claimed this yet.
bug
feature/data-management
team/product-analytics
team/query-performance
- Dominant language
- Python
- Stars
- 39.9k
- Forks
- 3.4k
- Avg merge
- 7h 27m
- Merged PRs (30d)
- 222
Description
Bug Description
Please describe.
User is seeing Failed to save columns to event definition on Data management > event > matching event after adding additional columns.
How to reproduce
- navigate to event under data management
- configure columns
- add new columns and save as default column.
Additional context
https://posthoghelp.zendesk.com/agent/tickets/36332 (moved to PostHog: https://us.posthog.com/project/2/support/tickets/38126)
Debug info
- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables or https://eu.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]
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
No source files, tests, or entry points are named. Start with the reproduction steps in Data management > event > matching event and review the linked support context to locate the save path; done means additional columns can be saved as the default without the reported error.
Written by the indexing model from the issue text.
Assessment
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100