Thanks for this example!
Do you think you could move the RPP closer to the HN with the same address? They seem to be too far from one another. I cannot always reproduce this issue, so I’ll check this with the team to confirm and potentially find some other root cause.
Hello!
I can’t make any changes to the place, because the request is blocking them. If the location was a problem then theoretically a random housenumber should work. I tried changing it to 431, but that didn’t help either.
Thank you for your response @LihtsaltMats. What I meant was moving the RPP whilst approving the PUR in the same save action. The number itself should not be causing this issue as I was able to add an RPP with the same address a bit closer to the HN (1). Either way, I have let the team know about this problem and will keep you posted.
Hello!
Yes, I’ve tried moving the POI in various places around the HN before making this report. Also tried different distances from the HN, as that has been a known issue as well. None of the usual solutions worked, so this report was the last resort.
Thank you for checking!
Thank you for the clarification @LihtsaltMats; the root cause is still unclear to me, so I hope the team will be able to find out more. There could be an issue on the client (app) end as well. The same applies to RPP PURs with missing HNs - there is no way to produce this type of request but somehow they end up like this in WME.