How to Solve This error (Server Is Busy The record was saved. However, the data could not be displayed because the server is busy)

Question

How do I solve this error that occurs after assigning a record to another user

Server Is Busy

The record was saved. However, the data could not be displayed because the server is busy. Click Try Again to try to display the data now, or click Cancel to continue to work. If you click Cancel, you can try opening the record later.

Answer 1

When the security role of the old owner is just having user-level read access, this error will be thrown - since that record is owned by the new owner after the Assign operation.

The error message is bit incorrect here. The error was because the user had User Level Read Access to the record or (Entity to be specific) and on saving the record, we had one of our real-time workflow being triggered which was assigning this record to another user. And on assignment, the record being getting assigned to another user, the user who had created\saved the record was losing the access to it.

Reference