Our Salesforce system has a private OWD for the Case object, with access opened up via Owner-Based Sharing Rules, Case Teams & the Role Hierarchy. We recently implemented assignment rules to start assigning Cases to queues. Users are now sometimes getting this error when they try to create a new Case:
After some investigation, it seems like the Case Assignment rules are causing this (turning them off makes the error go away). I can only assume the cause is that the assignment rules are making the creator lose access to the record.
Here's the weird part... The Case is still created in the background even if they receive this error! This has led to lots of Case duplication by Users because they keep retrying and getting the error. This seems very odd to me.
Has anyone experienced this before? Can anyone explain this behaviour?
My best guess at what's happening: Users are allowed to create the record, and then the assignment rules cause the User to lose access to it, which then prevents Salesforce from taking the User to view the record. Still, I would expect to be taken to the record, and just blocked from seeing it. I wouldn’t have expected an error to appear on the create screen, which makes it seem like the record was not created. Doesn't seem like expected behaviour??