Space Planner App, Overwrites, and Change Tracking (layerServerGens)

[AaronKoelker]

Hello. I'm in the testing/development phase of creating an Indoors project for our space planning folks, and am running into an issue with the Space Planner configurable app. Anytime I try and update my Indoors data (add a layer, add a field, change default symbology, etc.) and overwrite my Indoors feature service from ArcGIS Pro, the Space Planning app becomes unusable. I know that Plans most likely need to be recreated after these sorts of changes, however I'm not even able to create new Plans after overwriting the service. Worse, even deleting the entire Space Planning app and creating a new one from scratch leads to the same error below whenever I try to create a new Plan:

There was an error creating your plan.

Cannot read properties of undefined (reading 'layerServerGens')

Initially, the only fix seemed to be publishing an entirely new Indoors feature service (which worked until I inevitably needed to overwrite the data from ArcGIS Pro again, leading to the issue occurring once more). But after digging into the layerServerGens property, I saw it has to do with the layer's Change Tracking. I found that if I disable and reenable that property in the hosted feature Settings, it appears to clear the log and whatever is causing the inconsistency, and the Space Planner app is then able to create Plans again. I don't fully understand what's happening behind the scenes, however. To be specific, it is the setting to "Keep track of changes to the data (add, update, delete features)" which then creates a change log. This setting is required for the Space Planner app to function. 

So my question is, what exactly is happening here that causes the issue, and what can we do differently to avoid it? Do we simply need to check and uncheck this setting anytime we want to overwrite the service, and then have space planning staff create a new Plan?

I'm using ArcGIS Pro 3.4 and publishing to a single hosted feature service in ArcGIS Online with multiple end points. While I don't expect a need to make changes like this often once things get going (new fields, layers, symbology, etc.), I know it will come up from time to time as needs change and workflows evolve. The error leads me to believe I'm not approaching this the recommended way.