OR Channel Syncing is Failing

Yesterday and today I have been getting notices from OR of API syncing failures.

First with Airbnb. I added a couple dozen photos to each of my three listings yesterday, and soon after that OR sent me this error for each one:

• Airbnb limits photo deletes to 100 per week -- delete extra photos on the Airbnb UI or resync next week.

I deleted about 3 or 4 photos from each listing, not 100.

But I added around a couple dozen each. Yet OR sent triplicates of each of these to Airbnb, some copies of these being with no captions, when I had captions to all of them. And these multiples linger now, despite the ongoing syncing since then.

This is requiring these triplicates to be manually deleted from Airbnb's side. Will these triplicates continue to be fed to Airbnb, though?

I replied to the notifications of these but have heard nothing back about it from OR.

Is OR support ranking support requests about its technical flaws causing issues with listings as Urgent priority over and above all other support requests?

In addition to these photo issues, I am getting reports from OR of syncing failures with all my listings on Google Vacation Rentals, with this error:

• Push Extra Guest Charges PostPropertyExtraGuestChargesAsync failed, details 8136:error `StayDates` `application` attribute is invalid for `ExtraGuestCharges` message.

Request to OR support: Please prioritize as Urgent those technical flaws that are causing listing issues for hosts.

I'm extremely disappointing and find it totally unacceptable that it took three days to get a reply from OR support for the one technical glitch causing issues with my listings. And then I was told that the tech team will be notified and have a great weekend.

And it's more disappointing and unacceptable that haven't gotten a reply yet after three days about the second technical glitch causing issues with my listings.

Why aren't such issues getting prioritized as Urgent and treated as such?

This is an issue caused by an unannounced change implemented by Airbnb - as you pointed out, the error is being issued by Airbnb, not OwnerRez, and is widespread in effect across our Airbnb-connected clients.  We are attempting to work with Airbnb engineering for them to develop a less problematic approach, but at present this has not yet been achieved.

That being the case, using your new alert system to inform us about the status like this would be much appreciated, since support staff is hard-pressed to respond to every ticket on it.

Also, I'm not understanding why each new sync doesn't delete the duplicates.

And I haven't gotten a response from three days ago about the technical issue with GVR.

Thank you, Ken.