Mark Fields

@tyler-cai-microsoft I think we can close this for now, we deprioritized [AB#1068](https://dev.azure.com/fluidframework/235294da-091d-4c29-84fc-cdfc3d90890b/_workitems/edit/1068) until we can get a more cohesive plan for snapshot cache managements between the layers.

At first glance, some of this is related to #7995 so assigning myself here as well.

Unassigning myself for sprint planning/tracking purposes but still following!

This relates to discussions about having errors be returned through our APIs rather than thrown. Then we wouldn't be having to deal with errors in catch blocks which are `any`...

Putting under Epic https://github.com/microsoft/FluidFramework/issues/7999 for now, but there might be a better way to organize this work, stay tuned as part of Jan plan.

Goal for Jan is just to get a light design written up, will plan to execute in Feb (due to overfull Jan plan)

"This would be helpful in telemetry." -- I need to get a specific use case in here to prioritize. For now moving to March, if it bumps again it'll be...

I had a good conversation with the team about this issue today, discussing the approach in #9334. Main feedback was to step back and make sure the use case and...

@agarwal-navin -- You say "No" does not introduce breaking change, but you're targeting `next`. Why is that?

@WayneFerrao - Sorry I should have let you know - I just took care of this! #11499