FYI this is a consequence of a recent change to Kobo’s APIs to limit the maximum number of responses to 1000 per page, for performance issues, which came into effect earlier this month; from Important Changes to `/api/v2/assets/{uid_asset}/data` Result Limits
The maximum number of results per page will now be 1,000 (instead of 30,000)
We are working on a corresponding change to Kobo map feature to perform a paging request to fetch 5000 results, so that you can then display a maximum of 5000 points on the map.
This appears to have started recently. I’ve noticed it too, somewhat intermittently (but on all projects and all servers). If you look closely these all (rather alarming) 403 error appear to correspond to specific tiles on the map, and they will come and go if you zoom in and out, scroll back and forth across the maps. So I suspect it is the backend OSM tile server that is sometimes returning failures for some tiles being requested to render on the map.
We are investigating, but in the mean time if you refresh/zoom in-out/scan back-forth you can often get the missing tile to appear.
