Hello,
Please note that there is an issue when Customiser changes are being published in V15SP1HF10. This is a known issue and has been addressed and fixed in V15SP1HF11 which will be released to our offices from the R&D team, in late November this year. Unfortunately, due to all the Framework file changes, a standalone fix is not possible.
What can/does occur after a report, UI , etc. changes, have been published, is that the users see the below error within multiple modules , including the mobile technicians whereby their activities are coming up blank.

The interim solution to resolve this issue, is to perform an IISRESET. We would recommend that customers on V15SP1HF10 perform customiser changes after hours and perform an IISRESET immediately afterwards, to minimise the disruption to the business.
I have added some technical information regarding this issue below:
This issue occurs in environments with a number of application servers. When a metadata object like a db query is changed , we need to update this query on all application servers. We use windows file watcher to observe metadata file changes and also redis pub/sub to inform application servers about customisation changes. But sometimes both these mechanisms fail. To resolve this issue we added a new timer that will verify metadata files in the shared folder and metadata loaded into the process memory and if the metadata files on the disk are newer, the metadata in the memory will be updated.