Twenty•5mo ago

Errors thrown when adding fields

Hi twenty team, congrats on the recent release of v0.12 its great! When I try and add a new field to my company object (or any other object) I am getting a failure. I have attached a video of me adding the field, a screenshot of the error shown in the browser and a copy of the error thrown in the log. I upgraded to v0.12.2 yesterday, so that might be relevant, but I think the update went smoothly.

    InternalServerErrorException: GraphQL errors on favorite: {"message":"cannot pass more than 100 arguments to a function"}
        at computePgGraphQLError (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/utils/compute-pg-graphql-error.util.js:30:12)
        at WorkspaceQueryRunnerService.parseResult (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:284:80)
        at WorkspaceQueryRunnerService.findMany (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:61:21)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async field.resolve (/app/node_modules/@envelop/on-resolve/cjs/index.js:36:42)
        at async /app/node_modules/@graphql-tools/executor/cjs/execution/promiseForObject.js:18:35
        at async Promise.all (index 1) {
      path: [ 'favorites' ],
      locations: [ [Object] ],
      extensions: [Object: null prototype] {}
    }

    InternalServerErrorException: GraphQL errors on favorite: {"message":"cannot pass more than 100 arguments to a function"}
        at computePgGraphQLError (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/utils/compute-pg-graphql-error.util.js:30:12)
        at WorkspaceQueryRunnerService.parseResult (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:284:80)
        at WorkspaceQueryRunnerService.findMany (/app/packages/twenty-server/dist/src/engine/api/graphql/workspace-query-runner/workspace-query-runner.service.js:61:21)
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async field.resolve (/app/node_modules/@envelop/on-resolve/cjs/index.js:36:42)
        at async /app/node_modules/@graphql-tools/executor/cjs/execution/promiseForObject.js:18:35
        at async Promise.all (index 1) {
      path: [ 'favorites' ],
      locations: [ [Object] ],
      extensions: [Object: null prototype] {}
    }

Any help or suggestions would be greatly appreciated.

12 Replies

Rob•5mo ago

Perhaps I have hit this bug https://github.com/twentyhq/twenty/issues/5056

GitHub

Allow users to create more than 100 fields / compositeProperties in...

Bug Description If a user create more than 100 fields, we are hitting pg_graphql/postgres query limit. 100 can seem high but we are hitting it in the following queries: favorties / activityTargets ...

Rob•5mo ago

And incase its relevant, here is the object

marie•5mo ago

Hi Rob! thank you for your feedback, we are looking into it!

Rob•5mo ago

Awesome. Let me know if I can share anything else that will help.

marie•5mo ago

Hi again Rob - you have identified the right issue. It's something we will work on soon, in the meantime I have no real workaround to suggest to you, except to avoid creating this many fields, which is a serious limitation I know! As stated in the issue the problem is that we query all object's fields in some queries and hit the pg_graphql/postgres limit

Rob•5mo ago

Thanks Marie. Does the amount of options within a multi select matter? Or is it just the number of fields in the object? Also, is it the total number of fields across all objects? Or just the number of fields in this object? I appreciate you looking into this thanks

marie•5mo ago

You are welcome, thanks for the feedback. No, multi-select options are not in the query. It's the number of fields across all project

Rob•5mo ago

That’s great to know. So it’s the number of fields across all objects within the workspace that I need to keep minimised. Appreciate you helping here. I’m looking forward to this being addressed in a future release. I do think this is a limitation that many people will hit. But in the meantime, I’ll be cautious of how many fields I add. Thanks twenty team!

charles•5mo ago

@marie have we fixed this?

marie•5mo ago

charles•5mo ago

Ok! I feel we can address this one by changing the way we query Favorites. I have added some technical input here: https://github.com/twentyhq/twenty/issues/5056 and tagged it as good first issue

GitHub

Allow users to create more than 100 fields / compositeProperties in...

charles•5mo ago

closing this thread 🙂

Gaming

Programming

Errors thrown when adding fields