Skip to main content
Nintex Community Menu Bar
Question

Operation Too Large error for one user but not another user?

  • July 10, 2024
  • 10 replies
  • 15 views

Forum|alt.badge.img+5

Has anyone seen a scenario where one user gets an Operation Too Large error for one account, but when another user goes to that account it works just fine? It is definitely my Skuid page issue, but I’ve only seen this based on the specific record, not a specific user. The user that is getting the error can access other accounts without an issue.

This topic has been closed for replies.

10 replies

Forum|alt.badge.img+10

Thanks for bringing this to the community Ryan. Looks frustrating.

Do both users have the same permission set? Are they both retrieving the same amount of information from salesforce on the same page? My thought is that the two users might not be the same from Salesforce’s perspective.


Forum|alt.badge.img+5
  • Author
  • July 10, 2024

Hi Stephen - I have the same role/profile in SFDC as the user that is getting the error. But, I don’t get the error. Also - I had one user go to another page, then come back to that page and it worked. Seems pretty random right now.


Forum|alt.badge.img+5
  • Author
  • July 10, 2024

I have confirmed that the users have the same permission set. Any more detail on that one?

Between the user that is getting the error and the user that is not getting the error - same exact account, same permission set, same role/profile in SFDC.


Forum|alt.badge.img+5
  • Author
  • July 10, 2024

update - we found that when an account does not have a related opportunity, it will error out. When we do have an opportunity it works perfectly!

My question is - if I have deactivate condition set on my condition in that model that pulls in related opportunities, where else would I need to look to have it deactivate if none?

5a5d89794924e1b1e2e3012f7cba32220324093b.jpg


Forum|alt.badge.img+20

In that case, set to abort query.


Forum|alt.badge.img+5
  • Author
  • July 10, 2024

I had thought about that - unfortunately, when I changed it to abort, it didn’t clean up the error. Any other thoughts? I’m going to go through my other models that I have tied into Related Opportunities and see if maybe that cleans it up.


Forum|alt.badge.img+5
  • Author
  • July 10, 2024

Pat - you are amazing. I went through and added the Abort to all conditions calling the Related Opportunities model. That solved this mystery. How can I send you some gratitude??


Forum|alt.badge.img+20

I can jump onto a GTM in about 30 minutes.


Forum|alt.badge.img+20

Meh … I enjoy solving problems. 😛


Forum|alt.badge.img+20

Actually! You’d be my hero if you could solve my issue.

https://community.skuid.com/t/issues-connecting-to-dynamics365-online-data-source