Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Data Availability Date in API payload

  • 1.  Data Availability Date in API payload

    Posted 06-05-2025 18:19

    Christopher_Greene | 2021-03-29 16:39:21 UTC | #1

    Hi, I'm running the conversation results API,

    /api/v2/analytics/conversations/details/jobs/{jobId}/results

    and do not get results, but rather I get:

    { "dataAvailabilityDate": "2021-03-29T02:36:50Z", "conversations": [] }

    Is the time of day displayed local or GMT? If GMT, then I should have been able to pull my data assuming the time of day is PM, but if AM, then that makes no sense because that would have been last night EST.

    Thanks for any assistance on this. Chris

    tim.smith | 2021-03-30 21:38:45 UTC | #2

    "dataAvailabilityDate": "2021-03-29T02:36:50Z", Is the time of day displayed local or GMT?

    Per the ISO-8601 spec, a Z after the timestamp indicates UTC: https://en.wikipedia.org/wiki/ISO_8601#Coordinated_Universal_Time_(UTC)

    I don't know when you ran the query or what your interval was, but be sure to take note of how data availability works with analytics jobs. TLDR; job data availability is delayed by up to 24 hours. https://developer.mypurecloud.com/api/rest/v2/analytics/conversation_details_job.html#data_availability

    Christopher_Greene | 2021-03-30 22:18:45 UTC | #3

    Hi Tim, Thanks for the reply. I am running the same JobID today, and I get the same message but the date is the current day and time is offset some. This is a different problem now, like provisioning or something??

    Chris

    tim.smith | 2021-03-30 22:23:59 UTC | #4

    Can you share the request body, response body, and correlation ID from the response? I'm unable to pass judgment on the behavior without knowing the details; what's expected is subjective as the job data process is somewhat fluid.

    Christopher_Greene | 2021-03-31 13:22:48 UTC | #5

    I'm fetching a JobID via this URI: /api/v2/analytics/conversations/details/jobs

    This is the request body for fetching a JobID: { "interval": "2021-03-19T00:00:00Z/2021-03-21T23:59:59Z", "order": "asc", "orderBy": "conversationStart", "paging": { "pageSize": 1000, "pageNumber": 1 }, "conversationFilters": [ { "type": "or", "predicates": [ { "type": "dimension", "dimension": "conversationEnd", "operator": "exists", "value": null } ] } ] }

    This all worked fine until this past Monday.

    Christopher_Greene | 2021-03-31 14:44:22 UTC | #6

    Tim, I ran new JobIDs for the date intervals that were problematic, and I'm now getting payload. I have to wonder though, did this issue have something to do with provisioning? Or, did the JobID prove to be corrupted somehow? Either way, the issue seems to have resolved.

    system | 2021-05-01 14:52:07 UTC | #7

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 10442



Related Content