Hi,
Thanks for reaching out to us.
As you can see from the description of videoMaxDuration, the value for this field is required for video line items and must be greater than 0 if you are using the v202102 or a later API version. Do keep in mind that this field is in milliseconds, so you'd need to set it to 30,000 (for example) to represent 30 seconds. The UI would be reflecting a value of 30ms, and rounding it down to 0 seconds in this regard.
With that being said, can you kindly provide the complete SOAP request and response logs (SOAP logging must be enabled) as well as your network code so that we're able to further investigate this? You may send them via Reply privately to author option.
Regards,
|
||||||
Hi,
I know what you mean. However, before I can comment on the matter, I would need to check this further on my end and replicate the issue you've encountered if it's possible; which is why I would need the complete SOAP request and response logs to be provided. Once provided, I will then provide what I've come up with my investigation.
Hi,
Thanks for providing the requested information.
Again, as you can see from the description of the field videoMaxDuration from our documentation, the value for this field is required for video line items and must be greater than 0 if you are using v202102 or a later API version. You may check for the environmentType parameter when updating, and see if it is set to VIDEO_PLAYER, which would mean that the line item in question is of type video. That being said, kindly supply the line item with a videoMaxDuration that's greater than 0 to be able to bypass this error for both occasions. Let me know how it goes.
As for the UI, I'm afraid we're unable to comment further on their procedures when updating line items. I would recommend reaching out to the publisher support team via our Support options for further assistance as they have more familiarity with the UI.