I was having a similar issue with an area containing a corrupt relation (Potlatch relation node member number bug). Knowing the relation reference number I was able download the relation from the API/history page, manually correct it and upload it again. After this, the problem went away. Cheers, Simon.