# Wayspot Removed after Scanning

**URL:** <https://forum.8thwall.com/t/wayspot-removed-after-scanning/1406>\
**Category:** Technical Support\
**Tags:** vps, vps-locations\
**Created:** [May 20, 2024, 6:43pm UTC](https://forum.8thwall.com/t/wayspot-removed-after-scanning/1406 "2024-05-20T18:43:53Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dev\_Test](https://avatars.discourse-cdn.com/v4/letter/d/a183cd/32.png) [@Dev\_Test](https://forum.8thwall.com/u/Dev_Test)\
**Post date:** [May 20, 2024, 6:43pm UTC](https://forum.8thwall.com/t/wayspot-removed-after-scanning/1406/1 "2024-05-20T18:43:53Z")

</div>

My recently added location was rejected due to its nature. I am unsure why it was rejected, as I provided all the necessary information available to me at the time. I am using this location to trigger an AR experience through 8th Wall’s web-based AR, and it will only be used from May 23rd to May 30th.

Please accept this waypoint as time is of the essence. I have faced significant challenges, including adverse weather, to scan the current location multiple times. Adding another location would further impact my development time. I will ensure it remains updated as requested via Maverick on Discord.

location details as per URL

geospatial-browser/6.931438,79.842187,14.74,acf68a4777483b84b028f5d1440a7cfe.16

 ![Screenshot 2024-05-20 173645](https://us1.discourse-cdn.com/flex019/uploads/x8thwall/original/1X/58c039ebc584619620c3387008954075859b7a45.jpeg)

---

<div class="post-metadata">

**Author:** ![Richard\_de\_Mowbray](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.8thwall.com/richard_de_mowbray/32/193_2.png) [@Richard\_de\_Mowbray](https://forum.8thwall.com/u/Richard_de_Mowbray)\
**Post date:** [May 21, 2024, 10:29am UTC](https://forum.8thwall.com/t/wayspot-removed-after-scanning/1406/2 "2024-05-21T10:29:44Z")

</div>

I had this many times. The explanation I got was that it happens when they have a high workload. And it will be activated in 2-5 days. Which it was in my case. So just hang tight. Not a very helpful error message for sure.
