Skip to main content

We have just discovered that on 9/21 Media Items stopped being returned using the API in our production environment.  Update this is not a SNS issue it is a media items issue.

Great to see you in the Community @rgreen. Thank you for flagging this. I see that this is also currently a support ticket. I will update this thread when a solution is available.


We continue to have the issue.  In our test sandbox running /api/v4/media/aID]/?versions=1 properly returns the "mediaItems" node in the JSON.  Our production environment does not.  Anyone else seeing this issue?

 


Hi @rgreen. I noticed in the support ticket that webhooks have been re-enabled for your sandbox instance. Please let us know if it’s not working as expected.


The media items JSON issue is still happening for us but Jimmy is helping us appreciate him jumping in and helping!


Update From Support tooks us 18 Business days but our issue is resolved now.

 

“As a quick recap of this issue, we could reproduce the behavior in the production environment but not in Sandbox. All of our troubleshooting, including looking at the front-end settings, showed both Production and Sandbox were configured the same way. The Landscape team noted that this issue began after a fix was released to address inconsistent asset syncing via the InRiver integration. However, during our initial investigation, it didn't seem the timeout fix was the cause, as we expected the Sandbox environment to have the same fix as Production and would then exhibit the same issues.
 
We asked our developers to do a deeper investigation into this issue as we suspected the issue had to do with the backend configuration. As it turns out, we found out that the timeout fix was only applied to your production environment. Upon this discovery, we immediately started reversing the fix and restoring the API functionality. In our effort to provide a solution for your timeout issue, the team didn't realize the impact of the fix on the API response. Their main goal was a quicker response time, and the unfortunate by-product was that the API response was no longer being created with all the items when using specific attributes (in this case, versions=1).”

 

Our API issue is now resolved, and this can be closed


Reply