Hi Simon,
Based on the information you’ve share that does align with a caching issue on the endpoint we use to load the data in the background. I don’t believe this is due to a setting in Litespeed Cache as this is a tool we see used often without issue, as they usually do not cache admin based resources.
If you add a marker, then clear Litespeed Cache, do you see the marker become available immediately? If so, it may be there Cache REST API option preventing data from being cached, but as mentioned this isn’t something we see commonly unless the cache has specifically been set up to cache admin resources.
It may be a caching layer from your host, but we might have a solution within our settings to overcome this. Please try navigating to Maps > Settings > Advanced Settings > And enable the option named “Disable Compressed Path Variables“.
This option should prevent Rest API caching from affecting the plugin, without negatively affecting the overall caching configuration.