Portal Property Feeds and Diagnostics
From Standout Property Manager Wiki Help
Portal Property Feeds and Diagnostics
This guide covers Standout's outbound property-feed monitoring and support diagnostics.
Portal activity
The Feeds/Portals area can show queue state, errors, successful sends and recent portal activity for the configured destinations. The screen is designed as an operational summary, not as a replacement for the property record.
Recent-activity queries are deliberately limited to the newest records first so large historical feed logs do not make the page unnecessarily slow.
Rightmove
Standout keeps portal state so updates/removals can be sent using the appropriate channel. Where historic state is incomplete, diagnostics explain why a removal cannot be chosen safely. Authorised support tools can perform the appropriate preview/force action when required.
Portal preview/force-send controls are support functions and are not intended for ordinary agency users.
OnTheMarket
OnTheMarket property-feed diagnostics can test the configured RTDF/property connection separately from inbound lead handling. Current configuration should use the agency's correct OTM Network ID and certificate/secret settings supplied for the integration.
Zoopla
Zoopla property advertising and Zoopla Leads are separate concerns. Advertising diagnostics should not be confused with the OAuth/Leads setup described in Zoopla Leads API.
Status mapping
Standout maps its own property status into the status expected by each portal. If a portal appears to show a different state (for example Let/Let Agreed), use diagnostics and the property's feed history before forcing another update.
Failed or unsupported data
Portal payloads should only contain values supported by that destination. Standout may omit internal values that do not have a safe portal equivalent rather than sending an invented enum.