Incident Summary: We experienced an issue with FB ad creatives in Rivery, where the error message "Tried accessing nonexisting field (messenger_sponsored_message) on node type (AdCreative)" was triggered. This issue occurred from Monday, August 19th, 21:15 UTC until Wednesday, August 21st, 10:00 UTC.
Impact: This problem affected FB ad creative reports when "all fields" were selected in the UI, or when the field ‘messenger_sponsored_message’ was included in the report set.
Current Actions: We have deployed a fix, and Rivery runs should now be back to normal. If you wish to fetch the data before the next scheduled run, you can manually re-run the affected rivers. Otherwise, the next scheduled run will retrieve the data as expected.
Next Steps: We are closely monitoring the situation to ensure ongoing stability.
We apologize for any inconvenience this may have caused and appreciate your patience. For further assistance or inquiries, please submit a support ticket through the console.
Thank you for your understanding. Rivery Support Team
Posted Aug 21, 2024 - 10:45 UTC
Identified
Incident Summary: We are currently encountering an issue with FB ad creatives in Rivery. The error message is: "Tried accessing nonexisting field (messenger_sponsored_message) on node type (AdCreative)."
Impact: This issue affects FB ad creative reports when "all fields" are selected in the UI, or when the field ‘messenger_sponsored_message’ is included in the report set.
Current Actions: Our engineering team has identified the problem and is actively working on a resolution.
Next Update: We will update you as soon as a fix is deployed.
We apologize for any inconvenience this may cause and appreciate your patience. For further assistance or inquiries, please submit a support ticket through the console.
Thank you for your understanding. Rivery Support Team