justin/new-site
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
new-site/docs/TODO.md
justin 4638fbe3d2 umami: fix Goals/Funnels 'Something went wrong' (migrate saved reports to v3.1.0 schema) 
The saved Goal + Funnel reports used a pre-v3.1.0 parameters shape (urls/dateRange)
that umami 3.1.0's report schema rejects (400 -> 'Something went wrong'). Migrated
both reports in the umami DB to the current funnelReportSchema/goalReportSchema
(steps[], top-level dates, goal type/value). Verified funnel route now passes schema
validation. TODO updated/closed.
2026-06-12 20:17:09 -05:00

1.2 KiB
Raw Blame History

Performance West — TODO / Backlog

Analytics / Umami

  • Fix Umami Goals and Funnels "Something went wrong" — RESOLVED 2026-06-13. Root cause: the saved Goal and Funnel reports were created in an older umami version and stored parameters in a pre-v3.1.0 shape. umami 3.1.0's funnelReportSchema / goalReportSchema reject the old shape (HTTP 400 -> client shows "Something went wrong"). - Funnel old: {urls:[...], window, dateRange:{startDate,endDate}} v3.1.0 needs: {startDate, endDate, window, steps:[{type:'path',value,filters:[]}]} - Goal old: {dateRange:{...}} (no type/value) v3.1.0 needs: {startDate, endDate, type, value} Fix: migrated the two saved reports in the umami DB to the v3.1.0 schema (urls->steps, lifted dateRange to top-level dates, set goal type=url/value). Verified: the funnel route now returns 401 (auth-gated, schema valid) instead of 400; underlying data exists (3,195 -> 86 on the compliance funnel paths). NOTE: running v3.1.0 = latest; the "Failed to find Server Action ... older/ newer deployment" log lines are unrelated stale-browser-cache noise.