:hedgehog: PostHog is the leading platform for building self-driving products. Our developer tools – AI observability, analytics, session replay, flags, experiments, error tracking, logs, and more – capture all the context agents need to diagnose problems, uncover opportunities, and ship fixes. Steer it all from Slack, web, desktop, or the MCP.
Python ab-testingai-analyticsanalyticscdpdata-warehouseexperimentsfeature-flagsjavascriptproduct-analyticspythonreactsession-replaysurveystypescriptweb-analytics
[
{
"id": "3690924555",
"title": "Feature request: Compare against previous option for funnel insights",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nInternal context is available in this internal [Slack thread](https://posthog.slack.com/archives/C00000000AA/p0000000000000000)\n\nCustomer would be able to select two arbitrary intervals (week, month etc) and compare the % change in conversion between those two periods.\n\n## Describe alternatives you've considered\n\nHogQL breakdown like `toString(toISOWeek(timestamp))`",
"html_url": "https://github.com/PostHog/posthog/issues/42606",
"number": 42606,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"66B80F\",\"default\":false,\"description\":\"Feature Tag: Funnels\",\"id\":2755388931,\"name\":\"feature/funnels\",\"node_id\":\"MDU6TGFiZWwyNzU1Mzg4OTMx\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/funnels\"},{\"color\":\"22380D\",\"default\":false,\"description\":\"\",\"id\":4767009900,\"name\":\"team/product-analytics\",\"node_id\":\"LA_kwDODg-Tdc8AAAABHCLMbA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/product-analytics\"}]",
"created_at": "2025-12-03T16:21:28Z",
"updated_at": "2025-12-09T21:55:58Z",
"locked": false,
"state": "open"
},
{
"id": "3693703939",
"title": "Feature Request: Insights datepicker - Allow custom relative date ranges",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nExtend the datepicker to support custom relative ranges.\nFor example:\n- Start: `now-15d`\n- End: `now-1d`\n\n## Describe the solution you'd like\n\n<img width=\"668\" height=\"366\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5f63822f-ee2b-417e-b6c0-300a641ab852\" />\n\n\n### Debug info\n\n```shell\n- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/42665",
"number": 42665,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"22380D\",\"default\":false,\"description\":\"\",\"id\":4767009900,\"name\":\"team/product-analytics\",\"node_id\":\"LA_kwDODg-Tdc8AAAABHCLMbA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/product-analytics\"},{\"color\":\"B9A3C8\",\"default\":false,\"description\":\"Feature Tag: Insights overall\",\"id\":4827937122,\"name\":\"feature/insights\",\"node_id\":\"LA_kwDODg-Tdc8AAAABH8R5Yg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/insights\"}]",
"created_at": "2025-12-04T09:34:33Z",
"updated_at": "2025-12-04T09:35:17Z",
"locked": false,
"state": "open"
},
{
"id": "3699894266",
"title": "overhaul workflow metrics overview tab",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nWe have had a few complaints over the metrics overview screen:\n<img width=\"1079\" height=\"653\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7734caff-8bc4-4504-982d-591d78d9d4e2\" />\n\n## Describe the solution you'd like\nReplace the top level boxes of success, Failure, filtered with `started`, `in progress`, `persons messaged`, `completed`, \n\tthen below that show a graph of those numbers over time instead of the filtered graph\n\tthen below that show a table for each message, with sent, delivered, opened, unsubscribed numbers in the column\n\n## Describe alternatives you've considered\n\n\n## Additional context\n\n\n\n\n\n### Debug info\n\n```shell\n- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/42853",
"number": 42853,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2025-12-05T18:13:08Z",
"updated_at": "2026-01-21T18:28:33Z",
"locked": false,
"state": "open"
},
{
"id": "3691114033",
"title": "feature request(surveys): migrate to `/products`",
"body": "### Feature request\n\n## Is your feature request related to a problem?\ni've personally experienced lots of migration conflicts on surveys lol, + probably generally just a good idea to do this\n\n## Describe the solution you'd like\nmigrate to `/products` in main repo\n\n## Describe alternatives you've considered\ncontinue getting merge conflicts on the reg\n\n## Additional context\n\n\n### Debug info\n\n```shell\n- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/42614",
"number": 42614,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"AF2927\",\"default\":false,\"description\":\"\",\"id\":5696933156,\"name\":\"feature/surveys\",\"node_id\":\"LA_kwDODg-Tdc8AAAABU5BNJA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/surveys\"}]",
"created_at": "2025-12-03T17:08:22Z",
"updated_at": "2025-12-03T17:08:22Z",
"locked": false,
"state": "open"
},
{
"id": "3708652062",
"title": "Feature request: Configurable bin width for funnel Time to Convert histogram",
"body": "### Feature request\n\nTitle\nFeature request: Configurable bin width for funnel Time to Convert histogram\n## Is your feature request related to a problem?\n\nThe Time to Convert histogram calculates bin width dynamically based on max conversion time ÷ number of bins. This means bin boundaries shift when the data distribution changes, making it harder to track trends over time or compare across date ranges.\n## Describe the solution you'd like\n\nOption to set a fixed bin width (e.g., \"1 minute per bin\") instead of only choosing the number of bins. This would keep bin boundaries stable for consistent trend analysis.\n## Describe alternatives you've considered\nSQL insights\n## Additional context\nFrom https://posthoghelp.zendesk.com/agent/tickets/00000\n\n\n\n### Debug info\n\n```shell\n\n```",
"html_url": "https://github.com/PostHog/posthog/issues/42995",
"number": 42995,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"66B80F\",\"default\":false,\"description\":\"Feature Tag: Funnels\",\"id\":2755388931,\"name\":\"feature/funnels\",\"node_id\":\"MDU6TGFiZWwyNzU1Mzg4OTMx\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/funnels\"},{\"color\":\"22380D\",\"default\":false,\"description\":\"\",\"id\":4767009900,\"name\":\"team/product-analytics\",\"node_id\":\"LA_kwDODg-Tdc8AAAABHCLMbA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/product-analytics\"}]",
"created_at": "2025-12-09T00:56:33Z",
"updated_at": "2026-02-02T22:53:50Z",
"locked": false,
"state": "open"
},
{
"id": "3708654668",
"title": "Feature request: Median and percentile options for funnel Time to Convert",
"body": "### Feature request\n\nTitle:\nFeature request: Median and percentile options for funnel Time to Convert\n## Is your feature request related to a problem?\nThe Time to Convert view only shows average conversion time as a summary stat. Averages can be skewed by outliers, making median or percentiles (P50, P90, P99) more useful for understanding typical user behavior.\n\n## Describe the solution you'd like\nAdd aggregation options (median, P90, P99, etc.) alongside or instead of average in the Time to Convert summary.\n## Describe alternatives you've considered\nSQL insights\n## Additional context\nFrom https://posthoghelp.zendesk.com/agent/tickets/00000\n\n\n### Debug info\n\n```shell\n\n```",
"html_url": "https://github.com/PostHog/posthog/issues/42996",
"number": 42996,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"66B80F\",\"default\":false,\"description\":\"Feature Tag: Funnels\",\"id\":2755388931,\"name\":\"feature/funnels\",\"node_id\":\"MDU6TGFiZWwyNzU1Mzg4OTMx\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/funnels\"},{\"color\":\"22380D\",\"default\":false,\"description\":\"\",\"id\":4767009900,\"name\":\"team/product-analytics\",\"node_id\":\"LA_kwDODg-Tdc8AAAABHCLMbA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/product-analytics\"}]",
"created_at": "2025-12-09T00:58:16Z",
"updated_at": "2025-12-09T00:58:16Z",
"locked": false,
"state": "open"
},
{
"id": "3724315197",
"title": "Feature Request: Track email open rate with workflows",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nWhen sending an email with a workflow, open rate is not tracked, which is an essential metric in email marketing.\n\n## Describe the solution you'd like\n\nTrack email open rate with Workflows.\n\nOne way to do it could be adding an image beacon with the available HTML block, when the user opens the email and loads the image, it queries an API that sends an event to PostHog for that workflow step.\n\n## Describe alternatives you've considered\n\n- Using a third-party service that allows tracking via images\n\n## Additional context\nFrom: https://posthoghelp.zendesk.com/agent/tickets/00000\n\n### Debug info\n\n```shell\nKind: support\n\nTarget area: workflows\n\nReport event: http://go/ticketByUUID/cce56107-7960-43e5-b41d-64bde8ee8b6b\n\nSession: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019b0fb4-a156-770f-b834-1cf355d7abe9?t=2428\n\nExceptions: https://us.posthog.com/project/2/error_tracking?filterGroup=%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22key%22%3A%22%24session_id%22%2C%22value%22%3A%5B%22019b0fb4-a156-770f-b834-1cf355d7abe9%22%5D%2C%22operator%22%3A%22exact%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D%7D\n\nLocation: https://us.posthog.com/project/000000/workflows/019aed14-386d-0000-4f0e-696e6cba7e7d/workflow?node=action_function_email_3c18d330-b1ce-43ac-820f-fbfb72a639ba&mode=logs\n\nPersons-on-events mode for project: person_id_override_properties_on_events\n```",
"html_url": "https://github.com/PostHog/posthog/issues/43317",
"number": 43317,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"040BFC\",\"default\":false,\"description\":\"\",\"id\":7602988218,\"name\":\"team/cdp\",\"node_id\":\"LA_kwDODg-Tdc8AAAABxSxkug\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/cdp\"},{\"color\":\"e4e5fa\",\"default\":false,\"description\":\"\",\"id\":9555365910,\"name\":\"feature/workflows\",\"node_id\":\"LA_kwDODg-Tdc8AAAACOYtQFg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/workflows\"}]",
"created_at": "2025-12-12T17:53:45Z",
"updated_at": "2026-02-17T16:36:53Z",
"locked": false,
"state": "open"
},
{
"id": "3730905699",
"title": "Allow users to enable PostHog event capture from email/sms delivery, opens, link clicks etc.",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nFrom a user \"Are [email feedback metrics] captured as standard PostHog events that I can use in insights, funnels, and user profiles?\"\n\n## Describe the solution you'd like\n\nA way to enable events to be ingested in addition to the Workflow metrics around messaging use cases\nThis allows users to do some cool things, for example:\n- Build more useful metrics/viz around their messages / campaigns\n- Trigger workflows as a result of message interactions\n\n\n\n\n\n### Debug info\n\n```shell\n\n```",
"html_url": "https://github.com/PostHog/posthog/issues/43384",
"number": 43384,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"e4e5fa\",\"default\":false,\"description\":\"\",\"id\":9555365910,\"name\":\"feature/workflows\",\"node_id\":\"LA_kwDODg-Tdc8AAAACOYtQFg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/workflows\"}]",
"created_at": "2025-12-15T15:13:35Z",
"updated_at": "2026-02-03T15:54:45Z",
"locked": false,
"state": "open"
},
{
"id": "3744208718",
"title": "Ability for \"reverse\" funnels",
"body": "### Feature request\n\n## Is your feature request related to a problem?\nNo\n\n## Describe the solution you'd like\nWhen attempting to track why a user may have stopped using an app, it would be helpful to be able to set an end point for a Funnel report that works backwards through the final events of users that hit the selected endpoint (Application Backgrounded, for example). You can then create an inactive user cohort, allowing you to get an idea of what might have caused those users to go inactive (hitting a paywall, for example).\n\n## Describe alternatives you've considered\nCustom SQL could be used for this that generates a report, but it's not as easy to visualize common funnel paths.\n\n## Additional context\nAsked if this was possible via support ticket #44441, and was told it isn't at this time and was directed to report here :)\n\n\n\n### Debug info\n\n```shell\nNot applicable\n```",
"html_url": "https://github.com/PostHog/posthog/issues/43686",
"number": 43686,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2025-12-18T18:05:43Z",
"updated_at": "2025-12-18T18:05:43Z",
"locked": false,
"state": "open"
},
{
"id": "3760619542",
"title": "Feature Request: Better client/server integration for Next.js [bootstrapped] flags",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nOur current advice is to call `init` inside the Next.js `instrumentation-client.ts`. The problem with this is that `instrumentation-client.ts` only runs once per app launch - i.e. on initial page load. Therefore for subsequent navigations, feature flags won't get refreshed.\n\nWe also recommend using Next.js middleware for bootstrapping feature flags, usually by passing the bootstrap flag data on a cookie. Middleware runs on every request, but because flags have already been bootstrapped there's no way to use middleware to update the flags and take advantage of e.g. local evaluation.\n\nThere's also a risk that for users with long running sessions (i.e. because `instrumentation-client.ts` is only called once at startup), flags could get stale and there's no way to force a refresh.\n\n## Describe the solution you'd like\n\n* PostHog provided middleware so that users don't need to implement this for themselves\n* Automatically update flags stored by the client when the middleware returns updated values\n* PostHog's React hooks should automatically account for this so that the flag updates from the server are completely abstracted from users\n\n## Describe alternatives you've considered\n\nYou can force a refresh of flags client side, but users have to think about this up front and it might not be an obvious consideration.\n\n## Additional context\nFrom: https://posthoghelp.zendesk.com/agent/tickets/00000\n\n### Debug info\n\n```shell\nnull\n```",
"html_url": "https://github.com/PostHog/posthog/issues/43980",
"number": 43980,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"e2a8ea\",\"default\":false,\"description\":\"Feature Tag: Feature flags\",\"id\":2467424521,\"name\":\"feature/feature-flags\",\"node_id\":\"MDU6TGFiZWwyNDY3NDI0NTIx\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/feature-flags\"},{\"color\":\"67EA82\",\"default\":false,\"description\":\"\",\"id\":7547103326,\"name\":\"team/feature-flags\",\"node_id\":\"LA_kwDODg-Tdc8AAAABwdeoXg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/feature-flags\"},{\"color\":\"bfd4f2\",\"default\":false,\"description\":\"\",\"id\":8735068920,\"name\":\"sdk\",\"node_id\":\"LA_kwDODg-Tdc8AAAACCKaS-A\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/sdk\"}]",
"created_at": "2025-12-24T15:50:09Z",
"updated_at": "2025-12-29T19:43:06Z",
"locked": false,
"state": "open"
},
{
"id": "3767820831",
"title": "PostHog AI generates a JavaScript error when asked a question while the user is actively using the SQL Editor. The issue occurs when a user has executed a query in the SQL Editor and subsequently asks the PostHog AI (via the right panel) a question that results in a secondary SQL query being generated and executed. The error appears to be a client-side crash related to model creation or instance initialization (referencing `createModel` and `createInstance` in the application chunks). ",
"body": "\nSteps to reproduce:\n1. Open the SQL editor, enter and execute a query (e.g., `SELECT * FROM events LIMIT 1`).\n2. Open the PostHog AI sidebar.\n3. Ask the AI a question that triggers a SQL query (e.g., \"what's the revenue for the past 52 weeks?\").\n4. An application error occurs during the execution of the AI-generated query.",
"html_url": "https://github.com/PostHog/posthog/issues/44064",
"number": 44064,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"},{\"color\":\"aaaaaa\",\"default\":false,\"description\":\"\",\"id\":8209896716,\"name\":\"feature/posthog-ai\",\"node_id\":\"LA_kwDODg-Tdc8AAAAB6VkVDA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/posthog-ai\"},{\"color\":\"aaaaaa\",\"default\":false,\"description\":null,\"id\":8368656067,\"name\":\"feature/sql-editor\",\"node_id\":\"LA_kwDODg-Tdc8AAAAB8s-Oww\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/sql-editor\"}]",
"created_at": "2025-12-29T16:30:03Z",
"updated_at": "2025-12-29T16:30:03Z",
"locked": false,
"state": "open"
},
{
"id": "3781606746",
"title": "Feature request for the PostHog .NET SDK to support an external or shared cache provider (such as Redis) for local evaluation of feature flags.",
"body": "Currently, the .NET SDK only supports an in-memory local cache, which leads to inconsistent feature flag states across distributed environments where multiple application instances are running. When a client’s requests are handled by different instances, the lack of a shared state can cause \"flickering\" or inconsistent rollouts. The request seeks an officially supported way to configure a distributed cache to ensure strict consistency of feature flag states per client across all instances in a .NET deployment.",
"html_url": "https://github.com/PostHog/posthog/issues/44254",
"number": 44254,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2026-01-05T14:01:43Z",
"updated_at": "2026-01-05T14:01:43Z",
"locked": false,
"state": "open"
},
{
"id": "3789281283",
"title": "Posthog-Native Push notification support",
"body": "Workflow customers make use of email heavily today, but a Native PostHog push notification channel is a huge value add.\n\nIdeally PostHog will handle\n- Device token collection (via PostHog SDKs) on Android, iOS, Flutter, React Native and (depending on user demand) Web\n- Mapping device tokens to PostHog persons for convenience in Workflow configuration\n- Feedback of push notification delivery and/or engagement (again requires PostHog SDK use)\n\nHere is the implementation plan for the first iteration of Push in Workflows: https://github.com/PostHog/posthog/issues/45009",
"html_url": "https://github.com/PostHog/posthog/issues/44444",
"number": 44444,
"labels": "[{\"color\":\"e4e5fa\",\"default\":false,\"description\":\"\",\"id\":9555365910,\"name\":\"feature/workflows\",\"node_id\":\"LA_kwDODg-Tdc8AAAACOYtQFg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/workflows\"}]",
"created_at": "2026-01-07T15:43:09Z",
"updated_at": "2026-02-10T06:49:30Z",
"locked": false,
"state": "open"
},
{
"id": "3794041701",
"title": "Workflow metrics show NaN and Infinity",
"body": "### Bug Description\n\nFairly straight forward change I think, we could just hide the percentage portion when it's not showing a real number. This [test project has a reasonable example to check on](https://us.posthog.com/project/00000/workflows/01995655-0635-0000-7aba-d0452ec76290/metrics). But here's a screenshot:\n\n<img width=\"2168\" height=\"510\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0c9c7d9b-bcbe-4f30-8225-20f92f9c5b90\" />\n \n\n## Additional context\n\n\n\n### Debug info\n\n```shell\n- [x] 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]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/44576",
"number": 44576,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"},{\"color\":\"A07813\",\"default\":false,\"description\":\"https://posthog.com/teams/messaging\",\"id\":8315777188,\"name\":\"feature/messaging\",\"node_id\":\"LA_kwDODg-Tdc8AAAAB76iwpA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/messaging\"},{\"color\":\"e4e5fa\",\"default\":false,\"description\":\"\",\"id\":9555365910,\"name\":\"feature/workflows\",\"node_id\":\"LA_kwDODg-Tdc8AAAACOYtQFg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/workflows\"}]",
"created_at": "2026-01-08T19:03:51Z",
"updated_at": "2026-01-08T19:03:51Z",
"locked": false,
"state": "open"
},
{
"id": "3794053349",
"title": "Workflows metrics series chart improvements",
"body": "### Bug Description\n\nThere are a few improvements worth making to the metrics series chart for workflows.\n\n1. Explain what each series is\n2. Make each series human readable (billable_invocation is readable but we can present it nicely) \n3. Option to disable specific series in the chart. In some instances it is possible that one series could be much greater than others, making it difficult to read the chart for the other metrics. Being able to disable certain series metrics could alleviate that issue when a user encounters it.\n\n## Additional context\n\n\n\n### Debug info\n\n```shell\n- [x] 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]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/44578",
"number": 44578,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"},{\"color\":\"A07813\",\"default\":false,\"description\":\"https://posthog.com/teams/messaging\",\"id\":8315777188,\"name\":\"feature/messaging\",\"node_id\":\"LA_kwDODg-Tdc8AAAAB76iwpA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/messaging\"},{\"color\":\"e4e5fa\",\"default\":false,\"description\":\"\",\"id\":9555365910,\"name\":\"feature/workflows\",\"node_id\":\"LA_kwDODg-Tdc8AAAACOYtQFg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/workflows\"}]",
"created_at": "2026-01-08T19:08:12Z",
"updated_at": "2026-01-08T19:08:12Z",
"locked": false,
"state": "open"
},
{
"id": "3794775999",
"title": "PostHog AI (Max) incorrectly reports successful creation of insights even when the process fails due to API validation errors. The issue occurs because the AI generates insight payloads that lack the mandatory \"query\" wrapper, sending the query object (e.g., TrendsQuery) at the root level instead. This results in a \"PydanticOutputParserException\" with the error message \"Field required\" at location [\"query\"]. ",
"body": "\nAs a result, the AI provides users with names and links to insights that were never actually created in the database. The problem is observed when users ask the AI to generate trends or other insights. The core fix requires ensuring the AI assistant wraps the insight definition within a \"query\" field to satisfy API validation requirements.",
"html_url": "https://github.com/PostHog/posthog/issues/44592",
"number": 44592,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"},{\"color\":\"aaaaaa\",\"default\":false,\"description\":\"\",\"id\":8209896716,\"name\":\"feature/posthog-ai\",\"node_id\":\"LA_kwDODg-Tdc8AAAAB6VkVDA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/posthog-ai\"},{\"color\":\"30ef7e\",\"default\":false,\"description\":\"\",\"id\":8838318773,\"name\":\"AI\",\"node_id\":\"LA_kwDODg-Tdc8AAAACDs4KtQ\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/AI\"}]",
"created_at": "2026-01-08T23:07:15Z",
"updated_at": "2026-02-11T23:32:29Z",
"locked": false,
"state": "open"
},
{
"id": "3833761968",
"title": "This feature request seeks to add a \"2 weeks\" (bi-weekly) interval option to Lifecycle insights, which currently only supports hour, day, week, and month intervals.",
"body": "The user tracks venue lifecycle metrics (new, returning, resurrecting, and dormant states) and requires a 14-day cadence to match their business model and venue engagement expectations. Existing weekly intervals are too granular and noisy, while monthly intervals hide important activity changes. Adding this option would allow the user to better align analytics with their customer success workflows and accurately monitor venue health without resorting to custom SQL queries that lack the native lifecycle visualization.",
"html_url": "https://github.com/PostHog/posthog/issues/45434",
"number": 45434,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2026-01-20T13:31:38Z",
"updated_at": "2026-01-20T13:31:38Z",
"locked": false,
"state": "open"
},
{
"id": "3798794060",
"title": "chore(flags): Investigate Flags HyperCache overlap with Flag Definitions HyperCache",
"body": "### Bug Description\n\nThe `/flags` service reads feature flags for a team from a flags Hypercache (Redis -> S3 fallback). We also have a separate Flag Definitions Hypercache used to populate responses for `/local_evaluation`.\n\nThe question here is why are there two? Is it possible for one to build off the other? For example, could the flags hypercache be replaced by the flag definitions with cohorts cache?\n\nThe goal of this issue is to investigate this question and either come up with an implementation if the conclusion is we should consolidate. If we shouldn't consolidate, then we should close this issue.\n\n### Debug info\n\n```shell\n- [ ] 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]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/44700",
"number": 44700,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"e2a8ea\",\"default\":false,\"description\":\"Feature Tag: Feature flags\",\"id\":2467424521,\"name\":\"feature/feature-flags\",\"node_id\":\"MDU6TGFiZWwyNDY3NDI0NTIx\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/feature-flags\"},{\"color\":\"aaaaaa\",\"default\":false,\"description\":null,\"id\":9980667168,\"name\":\"team/flags-platform\",\"node_id\":\"LA_kwDODg-Tdc8AAAACUuTlIA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/flags-platform\"}]",
"created_at": "2026-01-10T00:38:54Z",
"updated_at": "2026-02-12T12:24:09Z",
"locked": false,
"state": "open"
},
{
"id": "3804066041",
"title": "Some kind of categorization/saving/staring for Posthog AI chats so",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\n*Please describe.*\n\n## Describe the solution you'd like\nI'd like to save a chat with Posthog AI for later.\n\n## Describe alternatives you've considered\n\n\n## Additional context\n\n\n\n\n\n### Debug info\n\n```shell\n- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/44774",
"number": 44774,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2026-01-12T12:14:20Z",
"updated_at": "2026-01-12T12:14:20Z",
"locked": false,
"state": "open"
},
{
"id": "3804132687",
"title": "Feature Request: Improve date picker UX with year/month navigation and manual date entry",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nThe current date picker requires excessive clicks when selecting dates far in the past or future. For example, selecting a date 12 months ago requires clicking the back arrow 12+ times. This creates unnecessary friction for common use cases like year-over-year comparisons or historical data analysis.\n\n## Describe the solution you'd like\nEnhance the date picker with:\n\n- Hierarchical navigation - Allow users to zoom out to month/year views and drill back down, similar to standard date pickers (e.g., clicking on the month/year header to select different years, then months, then days)\n\n- Manual date entry - Add a text input field where users can type dates directly in a standard format (e.g., YYYY-MM-DD or MM/DD/YYYY)\n\n- Quick jump controls - Consider adding year forward/back buttons alongside the existing month controls\n\n\n## Describe alternatives you've considered\nUsing the existing date range presets (Last 30 days, Last 90 days, etc.) - but these don't cover all use cases\n\n\n## Additional context\nFrom: https://posthoghelp.zendesk.com/agent/tickets/00000\n\n### Debug info\n\n```shell\nKind: feedback\n\nTarget area: analytics\n\nReport event: http://go/ticketByUUID/3fad85bc-e853-4b98-a350-c991f3553d5d\n\nSession: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019bace3-e519-7a24-ad23-29003de2bfe5?t=2695\n\nExceptions: https://us.posthog.com/project/2/error_tracking?filterGroup=%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22type%22%3A%22AND%22%2C%22values%22%3A%5B%7B%22key%22%3A%22%24session_id%22%2C%22value%22%3A%5B%22019bace3-e519-7a24-ad23-29003de2bfe5%22%5D%2C%22operator%22%3A%22exact%22%2C%22type%22%3A%22event%22%7D%5D%7D%5D%7D\n\nLocation: https://us.posthog.com/project/00000/insights/1GDcw7eX/edit\n\nPersons-on-events mode for project: person_id_override_properties_on_events\n```",
"html_url": "https://github.com/PostHog/posthog/issues/44779",
"number": 44779,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"22380D\",\"default\":false,\"description\":\"\",\"id\":4767009900,\"name\":\"team/product-analytics\",\"node_id\":\"LA_kwDODg-Tdc8AAAABHCLMbA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/product-analytics\"},{\"color\":\"249A0D\",\"default\":false,\"description\":\"changes concerning the users experience\",\"id\":7890859824,\"name\":\"ux\",\"node_id\":\"LA_kwDODg-Tdc8AAAAB1lT3MA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/ux\"}]",
"created_at": "2026-01-12T12:33:50Z",
"updated_at": "2026-01-12T12:33:50Z",
"locked": false,
"state": "open"
},
{
"id": "3809149416",
"title": "Dashboard card \"Show details\" displays wrong event name when using \"All events\" with SQL aggregation",
"body": "### Bug Description\n\nWhen creating a trends insight that uses \"All events\" with a custom SQL aggregation (e.g., uniq(properties.something)), the dashboard card's \"Show details\" modal incorrectly displays a specific event name (like \"Pageview\") instead of showing \"All events\" as selected.\n\n<img width=\"512\" height=\"796\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3c47764f-7840-40dc-a8d9-5b5be6598bbc\" />\n\n<img width=\"512\" height=\"578\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5f37ce09-749a-4d57-831d-5820c9ccfa55\" />\n\n\n## How to reproduce\n\n1. Create a new trends insight in PostHog\n2. Select \"All events\" as the event source (not a specific event like Pageview)\n3. Configure a custom SQL aggregation such as uniq(properties.something)\n4. Save the insight and add it to a dashboard\n5. View the dashboard and click \"Show details\" on the insight card\n6. Observe that it displays a specific event name (e.g., \"Pageview\") instead of \"All events\"\n\n## Additional context\n\n- Occurs on PostHog Cloud\n- Currently viewing dashboard ID: 000000 (Product Health)\n- The issue is specifically with the \"Show details\" modal display on dashboard cards, not with the insight editor itself\n\n### Debug info\n\n```shell\n- [x] PostHog Cloud, Debug information: Session: https://us.posthog.com/project/sTMFPsFhdP1Ssg/replay/019bb78d-fd97-7625-9147-a3b03c5b2d69?t=3810\nAdmin: http://go/adminOrgEU/00000000-0000-0000-0000-000000000003 (project ID 000000)\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/44896",
"number": 44896,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"}]",
"created_at": "2026-01-13T14:36:47Z",
"updated_at": "2026-01-13T14:36:47Z",
"locked": false,
"state": "open"
},
{
"id": "3830439811",
"title": "Nuxt 4 SSR applications using the bootstrap pattern experience feature flag variant inconsistency during hydration, leading to \"multiple exposures\" warnings and UI flickering.",
"body": "Although the application correctly fetches flags on the server via `posthog-node` and passes them to the client-side `posthog-js` via a shared state, the client-side `onFeatureFlags` listener frequently triggers after hydration with different variant values than those provided in the bootstrap configuration. This occurs despite using a stable `distinctId` (derived from Supabase or a persistent cookie) and setting `advanced_disable_feature_flags_on_first_load: true`. The issue results in polluted experiment data and suggests a discrepancy between how variants are evaluated or cached between the Node.js and JS SDKs during the SSR handoff. Affected versions include `posthog-js` ^1.310.1 and `posthog-node` ^5.18.0.",
"html_url": "https://github.com/PostHog/posthog/issues/45365",
"number": 45365,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"}]",
"created_at": "2026-01-19T16:30:08Z",
"updated_at": "2026-01-20T20:59:31Z",
"locked": false,
"state": "open"
},
{
"id": "3839560592",
"title": "overhaul metrics for node view",
"body": "### Feature request\n\nthis is different from but related to https://github.com/PostHog/posthog/issues/42853\n\n## Is your feature request related to a problem?\n\nUsers are complaining the metrics view of nodes are un-usable\n\nNone of these make much sense for users for example:\n\n<img width=\"839\" height=\"513\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/96c35565-82dc-4564-84c6-0d197e14dceb\" />\n<img width=\"881\" height=\"497\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/32aa4a7e-626c-4a30-947f-ad206558940f\" />\n<img width=\"861\" height=\"475\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2b36bc9d-ad04-4c44-ac80-410de25f02be\" />\n<img width=\"772\" height=\"468\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/291efe34-651b-4a30-ba00-c20bcbd16fc0\" />\n\n \n## Describe the solution you'd like\n- We should remove: failed, filtered, billable invocation, succeeded from the top level graph\n- We should show how many users have completed a node, and share type specific info for that node, eg for email nodes, how many sent, delivered, opened, unsub\n- these graphs should use ints in the axes, no decimals\n\n\n## Describe alternatives you've considered\n\n\n## Additional context\n\n\n\n\n\n### Debug info\n\n```shell\n- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/45617",
"number": 45617,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2026-01-21T18:43:48Z",
"updated_at": "2026-01-21T18:44:39Z",
"locked": false,
"state": "open"
},
{
"id": "3867466651",
"title": "feat(flags): prevent failed flag evaluations from overwriting cached values",
"body": "Currently, we allow cached flag overwrites on SDKs during transient errors on flag evaluations. Here is a breakdown of how this might happen:\n\n1. `/flags` endpoint fails to evaluate a specific flag due to some transient error, like a DB timeout\n2. The flag that failed to be evaluated is returned in the payload, from the `FlagDetails::create_error` function, as well as a top-level `errorsWhileComputingFlags` signal (coarse-grained, only indicates that something went wrong). This returns the failed flags as `enabled: false` [[source](https://github.com/PostHog/posthog/blob/master/rust/feature-flags/src/api/types.rs#L421-L438)].\n3. If the `errorsWhileComputingFlags` signal is true, the SDK will overwrite the flags by upserting them (it does something like `{ ...cached, ...new }`) [[source](https://github.com/PostHog/posthog-js/blob/main/packages/core/src/posthog-core.ts#L649-L652)]. That wouldn't be an issue if we omitted the flags with issues, but we don't (and I don't think we should, as the original issue proposes)\n4. After the overwrite, a flag that was set to true will be changed to false.\n\nWe can split this issue into two steps.\n\n- [x] Add more detail to the flags that failed to be evaluated using the `reason.description` field, that is currently just set to `None`, and return a more fine-grained `failed: boolean` field each one of the flags.\n* In the SDKs side, use the failed field to filter out just the flags that failed to be evaluated before applying the merge.\n - [x] JS-SDK\n - [x] Go-SDK\n - [x] Kotlin-SDK\n - [ ] Php-SDK\n - [ ] Ruby-SDK",
"html_url": "https://github.com/PostHog/posthog/issues/46204",
"number": 46204,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"e2a8ea\",\"default\":false,\"description\":\"Feature Tag: Feature flags\",\"id\":2467424521,\"name\":\"feature/feature-flags\",\"node_id\":\"MDU6TGFiZWwyNDY3NDI0NTIx\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/feature-flags\"},{\"color\":\"aaaaaa\",\"default\":false,\"description\":null,\"id\":9980667168,\"name\":\"team/flags-platform\",\"node_id\":\"LA_kwDODg-Tdc8AAAACUuTlIA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/flags-platform\"}]",
"created_at": "2026-01-28T21:20:23Z",
"updated_at": "2026-02-12T13:39:51Z",
"locked": false,
"state": "open"
},
{
"id": "3868387399",
"title": "The Feature Flag service is experiencing cascading latency failures caused by database connection pool exhaustion. Slow queries from outlier teams for persons and cohorts are saturating the shared `persons_reader` and `non_persons_reader` pools, causing service-wide P99 connection acquisition times to spike from ~4ms to over 600ms.",
"body": "\n**Core Issues:**\n* **Shared Infrastructure:** Person, cohort, and group queries share limited reader pools. Slow queries (5-10s) hold connections, starving fast queries (5ms) across all teams.\n* **Tight Coupling:** In `src/flags/flag_matching_utils.rs`, person and cohort queries execute sequentially on the same connection, preventing easy isolation.\n* **High Timeouts:** Current 5-10s statement timeouts and 20s acquisition timeouts allow pools to remain exhausted for long periods.\n\n**Proposed Solution:**\n* **Phase 1 (Immediate):** Reduce statement timeouts (to 2s-3s) and connection acquisition timeouts (from 20s to 5s) to ensure fast failure and prevent queue depth growth.\n* **Phase 2 (Architectural):** Refactor the flag matching logic to release connections between operations and split `persons_reader` into two distinct pools: `persons_reader` (for person lookups) and `cohort_reader` (for cohort queries).\n* **Phase 3 (Optimization):** Address `non_persons_reader` exhaustion by investigating HyperCache misses and potentially tuning cache TTLs or prefetching.\n\n**Key Metrics & Errors:**\n* **Error Types:** `query_canceled` due to statement timeouts; `flags_acquire_timeout_total` spikes.\n* **Latency:** Connection acquisition spikes to 400-670ms during exhaustion events.\n* **Pools Affected:** `persons_reader`, `non_persons_reader`, and `persons_writer`.",
"html_url": "https://github.com/PostHog/posthog/issues/46222",
"number": 46222,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"aaaaaa\",\"default\":false,\"description\":null,\"id\":9980667168,\"name\":\"team/flags-platform\",\"node_id\":\"LA_kwDODg-Tdc8AAAACUuTlIA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/flags-platform\"}]",
"created_at": "2026-01-29T02:27:39Z",
"updated_at": "2026-01-30T19:43:55Z",
"locked": false,
"state": "open"
},
{
"id": "3878066861",
"title": "Improve Kubernetes probes for feature-flag pods to prevent unnecessary pod churn and cascading failures during high traffic. The existing `/_readiness` endpoint blocks on `pool.acquire()`, which can take up to 20 seconds under load, exceeding the Kubernetes 2-second probe timeout and causing healthy but busy pods to be removed from rotation.",
"body": "\nThe solution introduces a three-tier readiness check strategy: \n1. A \"fast path\" that returns OK immediately if any database connections exist (`pool.size() > 0`).\n2. A cached reachability check (default 30s) to prevent reconnect storms.\n3. A fallback probe with a 500ms timeout. \n\nAdditionally, a new `/_startup` endpoint is implemented to perform a blocking parallel check of all database pools, ensuring connectivity before the pod accepts traffic. These changes decouple \"busy\" states from \"broken\" states, maintaining capacity during database pool exhaustion. Includes new configuration variables: `READINESS_PROBE_TIMEOUT_MS` and `READINESS_VALIDATION_INTERVAL_MS`.",
"html_url": "https://github.com/PostHog/posthog/issues/46457",
"number": 46457,
"labels": "[{\"color\":\"e2a8ea\",\"default\":false,\"description\":\"Feature Tag: Feature flags\",\"id\":2467424521,\"name\":\"feature/feature-flags\",\"node_id\":\"MDU6TGFiZWwyNDY3NDI0NTIx\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/feature-flags\"},{\"color\":\"aaaaaa\",\"default\":false,\"description\":null,\"id\":9980667168,\"name\":\"team/flags-platform\",\"node_id\":\"LA_kwDODg-Tdc8AAAACUuTlIA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/flags-platform\"}]",
"created_at": "2026-01-31T01:22:34Z",
"updated_at": "2026-02-12T13:39:48Z",
"locked": false,
"state": "open"
},
{
"id": "3880178321",
"title": "The Checkout not working in posthog.com/merch for stickers",
"body": "### Bug Description\n\nDescription\n- I was trying to buy a sticker at \"https://posthog.com/merch\" , when checking out the state gets stuck on loading and nothing happens other than the loading animation\n- it's only when checking out the stickers\n\n<img width=\"833\" height=\"461\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ecad35d1-c2ec-453f-8a52-14c95572362a\" />\n\n\n## How to reproduce\n\n1. Go to https://posthog.com/merch?state=cart, add an item\n2. Click on the Checkout button\n\n## Additional context\n- Not sure which all items it effects, The problem seems to be with only the stickers, could be an issue with the low cost of stickers. \n\n\n",
"html_url": "https://github.com/PostHog/posthog/issues/46483",
"number": 46483,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"}]",
"created_at": "2026-01-31T21:47:57Z",
"updated_at": "2026-02-11T23:22:40Z",
"locked": false,
"state": "open"
},
{
"id": "3885874094",
"title": "GitLab issue report",
"body": "### Bug Description\n\n<img width=\"1124\" height=\"655\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/4f6acd68-8e48-425d-a068-0b036c76d32c\" />\n\n### Debug info\n\n```shell\n- [ ] 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]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [x] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/46536",
"number": 46536,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"}]",
"created_at": "2026-02-02T13:14:20Z",
"updated_at": "2026-02-02T13:54:17Z",
"locked": false,
"state": "open"
},
{
"id": "3892095705",
"title": "Workflows: Support Microsoft Graph API For Teams Support",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nThe current method requires setting up a webhook, which is great for engineers but not optimal for end users. See [this ticket](https://posthoghelp.zendesk.com/agent/tickets/00000). They'd like to essentially set up the ability for their end users to enable notifications in Teams from within their app. \n\n## Describe the solution you'd like\n\nSupporting the Microsoft Graph API would be a much easier process for end users of other services provided by our customers.\n\n## Describe alternatives you've considered\n\n\n## Additional context\n\n\n\n\n\n### Debug info\n\n```shell\n- [x] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/46703",
"number": 46703,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"e4e5fa\",\"default\":false,\"description\":\"\",\"id\":9555365910,\"name\":\"feature/workflows\",\"node_id\":\"LA_kwDODg-Tdc8AAAACOYtQFg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/workflows\"},{\"color\":\"aaaaaa\",\"default\":false,\"description\":null,\"id\":10122045407,\"name\":\"team/workflows\",\"node_id\":\"LA_kwDODg-Tdc8AAAACW1In3w\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/workflows\"}]",
"created_at": "2026-02-03T16:27:03Z",
"updated_at": "2026-02-03T16:27:03Z",
"locked": false,
"state": "open"
},
{
"id": "3893587495",
"title": "In the LLM analytics trace view, tool responses containing certain content—specifically Markdown files with embedded HTML or XML-like tags—are being replaced with an `Invalid XML content` error message.",
"body": "This issue occurs when the tool response is being rendered with \"XML highlighting\" enabled. The problem was observed when a tool returned a README file containing `<img>`, `<div>`, and `<br>` tags. Disabling XML highlighting or switching to Markdown highlighting does not resolve the display error once triggered. The core issue lies in the trace viewer's XML parser failing to handle non-well-formed XML content (like standard HTML/Markdown) within tool outputs.",
"html_url": "https://github.com/PostHog/posthog/issues/46759",
"number": 46759,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"}]",
"created_at": "2026-02-03T22:44:00Z",
"updated_at": "2026-02-04T12:02:24Z",
"locked": false,
"state": "open"
},
{
"id": "3895614485",
"title": "Bug: Breakdown value conflict",
"body": "### Bug Description\n\n## Bug description\n\n*Please describe.*\nUsers cant run a breakdown by an event property named value. The root cause looks to be in posthog/queries/breakdown_props.py:303, where every breakdown expression is aliased as unquoted AS value.\n\n## How to reproduce\n\n1. Send an event with a property named value\n2. Go to Insights and create a Trends query for that event\n3. Add a breakdown by the event property value\n4. query fails\n\n## Additional context\nFrom: https://posthoghelp.zendesk.com/agent/tickets/00000\n\n### Debug info\n\n```shell\nnull\n```",
"html_url": "https://github.com/PostHog/posthog/issues/46804",
"number": 46804,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"},{\"color\":\"22380D\",\"default\":false,\"description\":\"\",\"id\":4767009900,\"name\":\"team/product-analytics\",\"node_id\":\"LA_kwDODg-Tdc8AAAABHCLMbA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/product-analytics\"}]",
"created_at": "2026-02-04T09:42:57Z",
"updated_at": "2026-02-04T09:42:57Z",
"locked": false,
"state": "open"
},
{
"id": "3895748864",
"title": "Add a warning pop up telling people that progress will be lost if they dont save the insight they're working on",
"body": "### Feature request\n\n## Is your feature request related to a problem?\nYes, I sometimes lose work because I'm working on an insight and I press the top left back arrow to go and do smth else (ex: create an action, cohort, etc) and I lose my work because I forget to save before leaving. \n\n## Describe the solution you'd like\nA pop up warning people that they're about to lose any unsaved progress. I think that's the easiest way. \n\n## Describe alternatives you've considered\nAutomatic saving. But this seems like it might get confusing fast. As a user, I would prefer the first option. \n\n## Additional context\nNone\n\n\n\n\n\n### Debug info\n\n```shell\n- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/46808",
"number": 46808,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2026-02-04T10:14:44Z",
"updated_at": "2026-02-04T10:14:44Z",
"locked": false,
"state": "open"
},
{
"id": "3898222684",
"title": "Feature request to add a \"this week\" date filter option to PostHog insights.",
"body": "Currently, the date picker includes \"today,\" \"this month,\" and \"last week,\" but lacks a \"this week\" option, forcing users to rely on the \"last 7 days\" rolling window. This inconsistency makes calendar-aligned weekly reporting difficult, as the rolling window does not match the start of the calendar week or align with the \"last week\" filter for week-over-week comparisons. The requested solution is a \"this week\" option that tracks data from the start of the current calendar week through the present, respecting the project's \"week starts on\" configuration. This affects the insights date picker and reporting consistency across the platform.",
"html_url": "https://github.com/PostHog/posthog/issues/46885",
"number": 46885,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2026-02-04T20:09:37Z",
"updated_at": "2026-02-09T15:23:19Z",
"locked": false,
"state": "open"
},
{
"id": "3902336792",
"title": "Show warning if incorrect templating usage detected (Hog vs. Liquid)",
"body": "Currently users can get confused by `{` vs. `{{` and we don't do much to help them become aware of this.\n\nSince workflows templating supports both Hog vs. Liquid (and the mode is set on the node level) we can easily show warnings if it looks like the wrong type is being used",
"html_url": "https://github.com/PostHog/posthog/issues/46989",
"number": 46989,
"labels": "[{\"color\":\"e4e5fa\",\"default\":false,\"description\":\"\",\"id\":9555365910,\"name\":\"feature/workflows\",\"node_id\":\"LA_kwDODg-Tdc8AAAACOYtQFg\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/workflows\"}]",
"created_at": "2026-02-05T16:04:04Z",
"updated_at": "2026-02-05T16:04:04Z",
"locked": false,
"state": "open"
},
{
"id": "3902976418",
"title": "Trace not found when some special chars are in the url",
"body": "### Bug Description\n\nTesting out LLM traces and I get 404 on some traces which are obviously there\n\n<img width=\"785\" height=\"427\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/21069461-e7dd-43b3-a4b7-d8f63dfc3078\" />\n\nWhen clicking on one of them it says:\n\n<img width=\"1005\" height=\"400\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0a1ffa83-47ce-470d-bbc4-4dac46cf33e9\" />\n\nUsing custom distinct id, event name, etc\nThe url is something in this format:\n`/llm-analytics/traces/[string]:[string]/[string]:[number]:[id]`\n\nNot sure if the `:` or the `/` trips up the routing.\n\n## How to reproduce\n\n1. \n2.\n3. \n\n## Additional context\n\n\n\n### Debug info\n\n```shell\n- [ ] 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]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/47019",
"number": 47019,
"labels": "[{\"color\":\"cc0000\",\"default\":true,\"description\":\"Something isn't working right\",\"id\":1805609875,\"name\":\"bug\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODc1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/bug\"}]",
"created_at": "2026-02-05T18:37:18Z",
"updated_at": "2026-02-05T18:37:18Z",
"locked": false,
"state": "open"
},
{
"id": "3907336592",
"title": "Feature Request: Unify date filtering options",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nRelative date range filters can be applied to event timestamps at insight level, but not through other date filters for timestamp properties. Users would like to filter event properties, for example '`user_created` in last 7 days'.\n\n## Describe the solution you'd like\n\nRelative date options here:\n\n<img width=\"996\" height=\"203\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1cd12988-b64a-4e35-9816-756f7b4aaeea\" />\n\n## Describe alternatives you've considered\n\nUse a SQL expression - e.g. `timestamp > now() - INTERVAL 7 DAY`\n\n## Additional context\nFrom: https://posthoghelp.zendesk.com/agent/tickets/00000\n\n### Debug info\n\n```shell\nnull\n```",
"html_url": "https://github.com/PostHog/posthog/issues/47141",
"number": 47141,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"},{\"color\":\"39AFE1\",\"default\":false,\"description\":\"Feature Tag: Property filters\",\"id\":3860190313,\"name\":\"feature/property-filters\",\"node_id\":\"LA_kwDODg-Tdc7mFdRp\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/feature/property-filters\"},{\"color\":\"22380D\",\"default\":false,\"description\":\"\",\"id\":4767009900,\"name\":\"team/product-analytics\",\"node_id\":\"LA_kwDODg-Tdc8AAAABHCLMbA\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/team/product-analytics\"}]",
"created_at": "2026-02-06T15:46:28Z",
"updated_at": "2026-02-06T15:49:02Z",
"locked": false,
"state": "open"
},
{
"id": "3915402260",
"title": "Knowledge Base for customer",
"body": "### Feature request\n\n## Is your feature request related to a problem?\n\nBuild knowledge base\n\n*Please describe.*\n\n## Describe the solution you'd like\nKnowledge base to give information to ai chat\n\n## Describe alternatives you've considered\n\nhttps://www.usepylon.com/\nou hubspot \n## Additional context\n\n\n\n\n\n### Debug info\n\n```shell\n- [ ] PostHog Cloud, Debug information: [please copy/paste from https://us.posthog.com/settings/project-details#variables]\n- [ ] PostHog Hobby self-hosted with `docker compose`, version/commit: [please provide]\n- [ ] PostHog self-hosted with Kubernetes (deprecated, see [`Sunsetting Kubernetes support`](https://posthog.com/blog/sunsetting-helm-support-posthog)), version/commit: [please provide]\n```",
"html_url": "https://github.com/PostHog/posthog/issues/47278",
"number": 47278,
"labels": "[{\"color\":\"a2eeef\",\"default\":true,\"description\":\"New feature or request\",\"id\":1805609883,\"name\":\"enhancement\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODgz\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/enhancement\"}]",
"created_at": "2026-02-09T09:33:35Z",
"updated_at": "2026-02-09T09:33:35Z",
"locked": false,
"state": "open"
},
{
"id": "3916615872",
"title": "experiment with adding an automated SDK maintenance workflow using agents",
"body": "use this https://github.github.io/gh-aw/\n\n",
"html_url": "https://github.com/PostHog/posthog/issues/47320",
"number": 47320,
"labels": "[]",
"created_at": "2026-02-09T14:14:20Z",
"updated_at": "2026-02-09T14:14:21Z",
"locked": false,
"state": "open"
},
{
"id": "9000000001",
"title": "chore(deps): bump posthog-js from 1.200.0 to 1.201.0",
"body": "Bumps [posthog-js](https://github.com/PostHog/posthog-js) from 1.200.0 to 1.201.0.\n\n---\n\n### Commits\n\n- See full diff in [compare view](https://github.com/PostHog/posthog-js/compare/v1.200.0...v1.201.0)\n\n---\n\n[](https://docs.github.com/en/github/managing-security-and-access/about-dependabots-security-updates#about-compatibility-scores)\n\nDependabot will resolve any conflicts with this PR as long as you don't alter it yourself.",
"html_url": "https://github.com/PostHog/posthog/pull/99001",
"number": 99001,
"labels": "[{\"color\":\"0366d6\",\"default\":false,\"description\":\"Pull requests that update a dependency file\",\"id\":1805609900,\"name\":\"dependencies\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5OTAw\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/dependencies\"}]",
"created_at": "2026-02-10T00:00:00Z",
"updated_at": "2026-02-10T00:00:00Z",
"locked": false,
"state": "open"
},
{
"id": "9000000002",
"title": "Feature flags not working on mobile",
"body": "Duplicate of #43980",
"html_url": "https://github.com/PostHog/posthog/issues/99002",
"number": 99002,
"labels": "[{\"color\":\"cfd3d7\",\"default\":true,\"description\":\"This issue or pull request already exists\",\"id\":1805609895,\"name\":\"duplicate\",\"node_id\":\"MDU6TGFiZWwxODA1NjA5ODk1\",\"url\":\"https://api.github.com/repos/PostHog/posthog/labels/duplicate\"}]",
"created_at": "2026-02-10T01:00:00Z",
"updated_at": "2026-02-10T01:00:00Z",
"locked": false,
"state": "open"
},
{
"id": "9000000003",
"title": "Release 2026.03 checklist",
"body": "- [ ] Feature flags migration\n- [ ] Update changelog\n- [ ] Notify customers\n- [ ] Deploy to production\n- [ ] Monitor Sentry for errors",
"html_url": "https://github.com/PostHog/posthog/issues/99003",
"number": 99003,
"labels": "[]",
"created_at": "2026-02-10T02:00:00Z",
"updated_at": "2026-02-10T02:00:00Z",
"locked": false,
"state": "open"
}
]