# Partner feed troubleshooting A received or applied feed is not proof of publication. Start with the delivery ID, receipt counts and individual row errors. A valid row may still need owner review, photos, authority review and moderation before it can become public. ## Request failures | Outcome / code | Check and recovery | |---|---| | `validation_failed` | Read `field_errors`. Check UTF-8, XML structure, version, sequence, UUID idempotency key, supported fields and file limits. Correct the request and use a fresh key. | | `unauthenticated` | Verify the feed ID, environment and `X-Partner-Token`. A rotated or revoked token will no longer work. Ask an authorized organization owner to restore the intended configuration; do not send secrets to support. | | `forbidden` | The signed-in owner action lacks the required organization permission or authentication state. Use the intended organization and complete required authentication. A machine token cannot perform owner actions. | | `not_found` | Verify source/delivery IDs and the active organization. A receipt from another organization is not accessible. | | `capability_unavailable` | Partner feeds are disabled in this environment. Keep the source paused and confirm onboarding/activation status. Repeated submission will not enable the service. | | `idempotency_conflict` | The UUID was already used with different XML bytes or a different dry-run setting. Retry exactly the original request if recovering its receipt; use a new UUID for a different intended request. | | `invalid_state` | Check sequence and receipt state. Dry runs cannot be applied. A stale receipt or unsupported target state cannot be forced through by retrying. Review current data and submit a fresh delivery when appropriate. | | `version_conflict` | Another action changed the source/receipt/listing after the version you reviewed. Reload, review the latest state and retry only the intended operation with the current version. | | `rate_limited` / HTTP 429 | The feed has reached its submission limit. Wait for the `Retry-After` duration and reduce sender frequency; preserve the original UUID and bytes when retrying the same request. | | Request too large | Reduce the XML below 524288 bytes and 100 listings. Split into separate ordered deliveries with new UUIDs and increasing sequences. Do not send compressed payloads. | | Connection timeout / temporary server failure | The request may have been accepted. Retry its exact bytes, UUID and dry-run setting with bounded exponential backoff and jitter. Inspect the returned receipt before submitting a new request. | ## Row failures - **Required field missing:** new listings need `property_key`, `space_type` and `title`; new properties also need street, city, region, ZIP and property type. The error identifies the field to supply. - **Invalid value:** use taxonomy keys, a real `YYYY-MM-DD` date, a supported state/DC code and a nonnegative decimal price. See the field dictionary. - **Duplicate external ID:** send one operation for an external ID in a delivery. Never recycle an ID for another property or space. - **Inventory mismatch:** source updates cannot change mapped inventory facts. Correct the source or have the owner review the property through the normal inventory workflow, then send a fresh preview. - **Target changed / conflict:** owner edits or listing lifecycle changes can invalidate an earlier preview. Review the current listing and resubmit; a receipt does not lock the listing indefinitely. - **Unknown withdrawal:** confirm that this source previously created the external ID. Another source's ID or a manually created listing is outside its mapping. - **Already off market / unchanged:** no withdrawal action was necessary. Check the current listing if you expected it to be live. ## Common questions **Why did hosted collection stop?** Open the connection and check its last attempt, safe error code, schedule and source-access status. The exact source must remain approved, its server credential must be available and a worker must run for scheduled collection. Use **Collect feed now** to check the configured source when collection is enabled. Ask support to review source access; never email the credential. **Pause scheduled collection** is available while intake is disabled and retains existing data. **Why did a refresh create no new receipt?** Unchanged content does not create another receipt. A source returning no content creates no removal instruction. Check the last result and existing receipt link. A partner must send explicit withdrawals, which an owner must apply, to take mapped listings off the market through the feed. **Can I enter any feed URL?** Sources are approved for one organization and connection. The owner selects an approved source; arbitrary URLs, redirects, private-network addresses, compressed files and credentials embedded in URLs are not accepted. See the [Rentari guide](rentari-integration.md) for source setup. **Why is an accepted listing not visible?** The API stages changes for explicit owner application. New records are drafts. Complete listing information, photos, authority and moderation checks in RentZoobi. No feed operation purchases promotion or publishes automatically. **Why did removing a record from my file not remove it from RentZoobi?** This is an incremental contract. Omission leaves the listing unchanged. Send `action="withdraw"` with no child fields and have the owner apply that receipt. **Why are photos missing?** XML v1 does not fetch or import external media URLs. Add licensed/authorized photos through the listing media workflow. **Why did my old receipt stop applying?** A newer applied sequence protects against stale availability or price data. Review the source's last received/applied sequence and submit an intentional correction with a new higher sequence. **Can I resend after rotating credentials?** Use the new credential for the same feed. Preserve the original UUID and bytes when recovering an uncertain request; rotation does not create a new inventory identity. If the source is revoked or the environment is disabled, coordinate recovery with the organization owner before resuming. Do not automatically create a replacement source because its inventory mapping would be different. **Can I send a Zillow, MITS or Yardi file unchanged?** Only RentZoobi XML v1 is specified here. A vendor adapter requires separately reviewed mappings and approval. Rename-and-send is not a compatibility check. ## Support handoff Contact **info@rentari.ai** with your organization/source name, environment, delivery ID, UTC timestamp, sequence, error code and a minimal redacted example. Keep all tokens, authorization headers, renter documents and private account data out of the message. Support routing and response timing are subject to the current onboarding arrangement; this guide promises no service-level target. Before sharing a feed, replace real addresses and content with synthetic values if they are not needed to reproduce the failure. [sample-invalid.xml](sample-invalid.xml) deliberately contains invalid values for testing; do not use it as a production template. [sample.xml](sample.xml) is the starting template.