Legacy Dev Forum Posts

Drew_Banin | 2017-09-27 21:57:45 UTC | #1

Hello,

I'm trying to use the historical adherence endpoint to pull historical adherence data for all agents in my org. I'm hitting a bit of a snag, in that I can't seem to get the Notifications piece of this puzzle working.

I am debugging this using the Purecloud Notification Tester, and Postman for REST request debugging. Right now, I am trying:

1. Subscribe to historical adherence query notifications for a single user. My topic looks like:

v2.users.xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx.workforcemanagement.historicaladherencequery

where the x'd out string is an agent User ID.

2. POST to the historical adherence query endpoint for the Management Unit which contains the above user:

POST https://api.mypurecloud.ie/api/v2/workforcemanagement/managementunits/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy/historicaladherencequery

Body:
{
   "startDate": "2017-08-25",
   "endDate": "2017-09-01",
   "userIds": [
   		"xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
   	],
   "includeExceptions": true
}

> Response: 202 Accepted
{
    "id": ".........",
    "queryState": "Processing"
}

When I check the Notification Tester log, I only see Heartbeat events. From the documentation, it sounds like I should eventually see a notification with a download url. Is anyone able to tell me if I'm doing something obviously wrong here? I'm happy to provide more information here if needed.

Thanks in advance

matthew | 2017-09-27 23:56:22 UTC | #2

Hi Drew, In our tests we had to wait over 14 hours for a response on this notification topic. My developers are very patient :)

It did eventually give us the downloadurl.

We have raised a help desk ticket to see why its so slow.

matthew

Drew_Banin | 2017-09-28 04:14:22 UTC | #3

Thanks for the insight, Matthew. That is.... suboptimal. I just kicked off another historical adherence query -- I'll leave it running overnight and can report back on the results in the morning.

tim.smith | 2017-10-02 16:14:53 UTC | #4

This is definitely not working as intended. It shouldn't take more than a few minutes for an export to complete. Please open a ticket with PureCloud Support to investigate. They will need the correlation ID of the API request that initiated the export.

Behymer_Joe | 2017-10-02 17:14:03 UTC | #5

Hi Drew. I'm a developer on the team that wrote this endpoint, I'll do whatever I can to help you.

Tim is right, it should take between seconds and a handful of minutes if you ask for a lot of days or have a lot of agents.

From the post data you included, I think I found your correlation ID in our logs. Unfortunately it says the request completed quickly in under a second. We're going to keep digging on our side to see what the problem might be.

In the meantime, it would help me out if you were able to run a similar query through the PureCloud UI (same/similar dates, agents). If it returns data quickly, then maybe we can diff your query and the one the UI made in the network tab and learn something? If it doesn't return quickly then we'll have more data to go on to fix this.

Behymer_Joe | 2017-10-04 17:41:36 UTC | #6

I did some more digging. It seems there is another user in the same "org" you are using that is making successful historical adherence queries from our UI. I think that rules out your data.

Can you share with me the user ID you are using? Is it feb646*? It seems that some of our other services don't know about that user ID, while I research - do you happen to know how it was created, or was it deleted before, or anything like that?

If it is that user, feb646..., our system says it is deleted or otherwise missing. Please try another user account.

system | 2017-11-03 13:48:57 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: 1872