You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently these properties are not published, so the issue is not critical. However they are flooding the external errors, and we might want to handle these expected exceptions and handle them better.
Ciirus suggest we contact the host to ask for complete property details:
The most ideal method is that if the user has not defined rates, the unit is disabled, the user is notified, and once they have corrected the issue, they would notify you to re-enable it. I am not sure if this is feasible from a user experience perspective, so your suggestion sounds right, but if a user had a good number of units without rates, they will not be transacting. This would mean system utilization from both of our companies without any prospect of payment for this service. One way or the other, I think the crucial difference to your suggestion which is very necessary would be to notify the PM/Manager so they know why their units are not booking. They may not check very closely in all cases how many units have been disabled.
Solution
Do not create external_errors, but record these occurrences somewhere else, so that we can contact the hosts later if it makes business sense.
As #260 patch is, the error is just silenced, and we may lose data on a potential area to increase the inventory.
The text was updated successfully, but these errors were encountered:
Ciirus host has a lot of freedom, and sometimes they publish properties with invalid details.
This is a common issue the caused a number of errors:
Currently these properties are not published, so the issue is not critical. However they are flooding the external errors, and we might want to handle these expected exceptions and handle them better.
Ciirus suggest we contact the host to ask for complete property details:
Solution
Do not create external_errors, but record these occurrences somewhere else, so that we can contact the hosts later if it makes business sense.
As #260 patch is, the error is just silenced, and we may lose data on a potential area to increase the inventory.
The text was updated successfully, but these errors were encountered: