RVR-SRCHADN-009
- 1 Minute to read
- Print
- DarkLight
- PDF
RVR-SRCHADN-009
- 1 Minute to read
- Print
- DarkLight
- PDF
Article summary
Did you find this summary helpful?
Thank you for your feedback
Issue Summary
- The error
RVR-SRCHADN-009
occurs because there is a mismatch between the number of custom fields configured in the River setup and those returned in the API response from thesearch_ads_360_reporting
connector. This discrepancy commonly arises when the data schema returned by the API has changed, but the River configuration has not yet been updated to reflect these changes.
- The error
Action Steps:
- Verify Custom Fields Configuration: Ensure that the custom fields specified in your River configuration match the current schema of the API response. You may have to refer to the API documentation to verify the field names and types.
- Refresh Field Mapping: If there have been updates to the API, it might be necessary to refresh or update the field mappings in Rivery to align with the new schema. Check if new fields need to be added or existing ones need modifications in their configurations.
- Reconfigure the River: In Rivery, navigate to the field mapping section of your River and manually adjust the field configuration to ensure all expected fields are present and correctly mapped.
- Test Changes: After making the necessary adjustments, run the River again to check if the issue has been resolved.
External References:
- For more information on configuring rivers and handling API schema changes, consult the Rivery Documentation as well as the Search Ads 360 API Documentation to ensure you have updated information on field mappings .
If the issue persists or you need further assistance, please open a ticket with Rivery support.
Was this article helpful?