IncorrectResultSizeDataAccessException: Query { "$java" : Query: { "unpublishedAction.name" : "Query1", "unpublishedAction.pageId" : "600...

[sentry-io[bot]]

Sentry Issue: APPSMITH-DE

IncorrectResultSizeDataAccessException: Query { "$java" : Query: { "unpublishedAction.name" : "Query1", "unpublishedAction.pageId" : "6004a8da5b452f525458d9cc", "$and" : [{ "$or" : [{ "deleted" : { "$exists" : false}}, { "deleted" : false}]}, { "$or" : [{ "policies" : { "$elemMatch" : { "users" : { "$all" : ["jonas.bark@ffuf.de"]}, "permission" : "manage:actions"}}}, { "policies" : { "$elemMatch" : { "groups" : { "$all" : []}, "permission" : "manage:actions"}}}, { "policies" : { "$elemMatch" : { "users" : { "$all" : ["anonymousUser"]}, "permission" : "manage:actions"}}}]}]}, Fields: {}, Sort: {} } returned non unique result.
    at org.springframework.data.mongodb.core.ReactiveFindOperationSupport$ReactiveFindSupport.lambda$one$2(ReactiveFindOperationSupport.java:145)

[nidhi-nair]

I got to this state without triggering a Sentry issue, I'm not sure which one's the bigger problem :D

[trishaanand]

Opened issue #4013 for the underlying cause which lets actions with same name to be created in the page without server throwing an error. If there are no duplicate action names in the page, then the IncorrectResultSizeDataAccessException would not be thrown. That is a valid exception because somehow duplicate action names exist in the page.

[nidhi-nair]

@trishaanand I did this by opening the app in two pages and creating an API in each at the same time. This is a consistency issue. Also I wasn't able to get to the exception itself with this.

[trishaanand]

@nidhi-nair : This is because client was the only party enforcing unique names and the server wasn't. To reproduce this particular exception, you should try changing the name of any of these duplicate names Api's.