API Bug - Bulk Activity Status Reports Incorrect Start time

Hi,

 

I ran a bulk upload to add new contacts (was a test where it added a single contact).

When looking up the activity status I get this (snippet from json result):

 

 

"state": "completed",
  "started_at": "2021-11-18T16:52:01Z",
  "completed_at": "2021-11-18T16:52:01Z",
  "created_at": "2021-11-18T16:51:50Z",
  "updated_at": "2021-11-18T16:52:01Z",

 

 

I would assume that the process started creating contacts from the start date/time and finished at the completed date/time.

However in my test, the contact had a created date/time of "2021-11-18T16:51:50Z" which matches the created date/time of the bulk process.

 

But the documentation says: 

  • "started_at": (stringread only)Timestamp showing when we began processing the activity request, in ISO-8601 format.
  • "completed_at": (stringread only)Timestamp showing when we completed processing the activity, in ISO-8601 format.
  • "created_at": (stringread only)Timestamp showing when we created the activity, in ISO-8601 format.

See https://v3.developer.constantcontact.com/api_reference/index.html#!/Bulk_Activities/getActivity

 

This implies that if a bulk process is creating new contacts, it should have started doing so from the start date/time.

1 reply

Leaderboard