I addressed this with the engineering team and to be honest, they don't know how this was possible because this source is not supposed to extend results beyond 200 records even if you press the "Fetch additional results" so it appears it just stalled out/broke that last time. As it's mentioned in the integration, it works best with small imports at a time. To get more results that more than likely meet the criteria you need, you can run a new map search in a slightly different location than what was initially searched in and keep repeating the process so it can actually import fresh and more than likely relevant results.
The team is checking on how to stop that loading icon but seems like it's just glitched but not actually doing anything. Let me know if you happen to run another search and importing it to this same table causes any issues or also makes the new import behave the same way
This import limit is unfortunately set by the provider because that's the capacity this query/provider can offer for each unique request, and why running multiple separate searches is better after that number is maxed out. So this issue you ran into is actually a bug and shouldn't have been possible to go beyond so many records (which also raises the concern if many of those extra records are relevant to your query)You can still import all of them to the same table anyway. Hope this helps clarify a bit more!
.png){kind=logo}
