The probe post-processing script customizations are not syncing intermittently and requiring MID restartIssue As part of development and customizations to probe's post-processing scripts, changes may not be reflected on the MID Server immediately after the change. Changes should be synced automatically and immediately.ReleaseAll with Discovery plugin installed.CauseThe synchronization of these changes is done via the business rule Discovery - Flush ProbeResults cache. Following are most common causes with probe customization sync with MID Servers. 1. The probe caching is enabled on that probe by setting "Cache Results" (cache_results) to true. 2. The caching within the probe parameters that might skip the sync.ResolutionSet the property glide.discovery.disable_mid_probe_cache to true. Note This property is intended to be used in sub-prod instances only. The impact of this is not tested and is not recommended for production instances.