DCM API & CM360 joint error, possible date settings bug

[SzuYu00]

I was advised by dcm-support that I should try contacting the dcmapi-support for an error I’ve been running into, and they suggested that I contact the developer's specialist support team here.

My team has been facing a possible bug, which seems to involve both the API and CM360 Dashboard.

Since late June one of our application has been facing an ”TypeError: 'int' object is not iterable”

When calling

service = dfareporting_utils.setup([])

……

service.placements().insert(profileId=_profile_id, body=placement)

with the placement payload as

placement['pricingSchedule'] = {

                                'startDate': _start_date,

                                'endDate': _end_date,

                                'pricingType': 'PRICING_TYPE_CPM'

                }

This is part of a script where we try to create placements through CM360 API. It has been used on a weekly basis for the past 2 years and from past experience, ”TypeError: 'int' object is not iterable” at this section of the script is usually caused by conflicting date ranges, i.e. placement start, end date outside of campaign date range.

However, upon inspecting the CM360 dashboard, the campaign date range well includes the intended placement schedule.
For further investigation, we tried importing a spreadsheet via CM360 dashboard and received an error:
Failed:"Placement pricing period start date 2023-08-22 must be before or same as end date 2023-05-12.;Placement pricing period end date 2023-05-12 must be in placement date range 2023-08-22 - 2023-09-08"

Oddly, the date 2023-05-12 is nowhere to be found in any of our settings and even after trying different campaigns, the same 2023-05-12 is popping up in error reports.

Given the timeline of events and that they both happen during placement creation, I believe both errors are caused by the same root cause. In addition, if we upload the spreadsheet in legacy format on the CM360 dashboard, we will not receive an error, which makes me believe this could possibly be a bug. Given such, I am not aware of any parameter that will allow me to alter my API call to legacy mode and it also does not appeal to the established workflow of my team. I’ve tried looking up if there were any major API changes late June but wasn’t aware of any and since the CM360 Dashboard also produces a seemingly related error, I highly suspect that the API error is related to this date that is repeatedly appearing during Import Spreadsheet. Since the error is more obvious on the CM360 dashboard side, I tried contacting the dcm-support team first, but has had no progress to solving this issue for the past two months.

I would really appreciate if attention can be raised for the issue I am facing right now.

Attached is a sample of the downloaded result when uploading from the dashboard.
sheet_9807514.xls