Analytics tracking mutation error in v0.35.0 - Unknown argument "type" on Mutation.track error on lo
The error appears immediately upon accessing the login page
All other services appear to be running normally
Database initialization completed successfully
There is a version difference between frontend (0.3.3) and server (v0.35.0)
Steps Taken
Successfully initialized database with demo workspace using database:init:prod
All pods are running correctly:
twentycrm-server
twentycrm-front
twentycrm-redis
twentycrm-worker
Added TELEMETRY_ENABLED: false and ANALYTICS_ENABLED: false to both server and frontend deployments
The error persists after these changes
What We've Tried
Database reinitialization with demo workspace
Disabling analytics and telemetry on both server and frontend
Verifying all services are running correctly
Issue Description
When accessing the login page, we get GraphQL mutation errors in the browser console:
Uncaught (in promise) ApolloError: Unknown argument "type" on field "Mutation.track".
Unknown argument "data" on field "Mutation.track".
Field "track" argument "action" of type "String!" is required, but it was not provided.
Field "track" argument "payload" of type "JSON!" is required, but it was not provided.
Environment Setup
- Server:
twentycrm/twenty:v0.35.0
- Frontend: twentycrm/twenty-front:0.3.3
- Deployment: Kubernetes
- Database: PostgreSQL
- Server Base URL: https://mgenial.olhai.app.br
Configuration
Server Environment Variables:
```yaml
- PG_DATABASE_URL: postgres://twenty:[email protected]:5432/twenty
- NODE_ENV: production
- PORT: 3000
- REDIS_URL: redis://twentycrm-redis.twenty.svc.cluster.local:6379
- TELEMETRY_ENABLED: false
- ANALYTICS_ENABLED: false
- NODE_ENV: production
- PORT: 3001
- REACT_APP_SERVER_BASE_URL: https://mgenial.olhai.app.br
- VITE_SERVER_BASE_URL: https://mgenial.olhai.app.br
- VITE_GRAPHQL_URL: https://mgenial.olhai.app.br/graphql
- TELEMETRY_ENABLED: false
- ANALYTICS_ENABLED: falseTwenty
A modern open-source CRM
2 Replies
Hi! We have deprecated twenty-front some time ago (happy to see that you still have the old config meaning you are a early adopter!). You don't need to host the frontend anymore, it will be hosted by twenty container too (both server and frontend)
Please update your setup
Here is an updated docker-compose for 0.35.0
https://raw.githubusercontent.com/twentyhq/twenty/refs/tags/v0.35.0/packages/twenty-docker/docker-compose.yml
you can take inspiration from it to update your kube setup
Thx….. issue solved!!!