Internal 500 Error

[scottstrongLS]

Hello,

I recently inherited a project within my company after a former employee left for a platform built on top of Fluid Framework and I have very little understanding of how Fluid Framework works. Since he left, I have not made any changes to the code and the application has been running without issue for over a month. Just yesterday, however, some of the workspaces within our application have stopped loading (~30%) and the browser logs are showing a 500 error related to the fluid relay. I am not certain what this means. As I mentioned before, I have changed nothing within the code of the application and the error is not appearing in all workspaces, but seemingly at random (there is no discernable pattern attaching the error to particular users or groups within the application).

My question here is to ask if there have been any recent changes that could have affected my application that aren't related to code changes or updates (unless they are updates that would somehow automatically apply without my initiating them).
Are there any sort of usage restrictions or authentication keys that may have expired? I am just entirely in the dark on what to do.

Alternative to those questions, if there are any suggestions for potential methods to troubleshoot my system they would be greatly appreciated! I'm at the point where I do not even know where to begin looking to solve an issue like this!

Thank you!

[scottstrongLS]

Additional details with further investigation.

The issue mentioned seems to be related to the following error R11s fetch error: Failed to persist update to document session

[scottstrongLS]

As of yesterday morning, this error message has disappeared and the unusual behavior has stopped. I've kept an eye on it since then and not seen the issue resurface. As far as I am aware, nothing was done on my end to resolve the issue, but it disappeared all the same. My only guess is that the issue may have been a lingering problem attached to the mid-May 2024 Update that was published a week or so prior to the issue's first appearance. An additional patch was made on May 23rd that seemed to address client-side permissions in some capacity and I believe this may be what resolved the issue.

Either way, I am no longer experiencing the issue for now!

[nmsimons]

@scottstrongLS, without more details I couldn't say for sure but the issue may have been the result of an intermittent service issue. I'm not aware of any specific issue but that may have been the culprit.