Julio29 | 2023-10-27 20:10:24 UTC | #1
Good day!. Please, support us with the following.
I have a problem in the response of the Conversation Details Job API. I enter the following query,
{
"interval": "2023-10-26T05:00:00.000Z/2023-10-27T04:59:59.999Z",
"groupBy": [
"queueId"
],
"filter": {
"type": "and",
"clauses": [
{
"type": "or",
"predicates": [
{
"type": "dimension",
"dimension": "queueId",
"operator": "matches",
"value": "ae2c3168-232c-49f5-8195-afbbfcc7b11d"
}
]
}
],
"predicates": [
{
"type": "dimension",
"dimension": "originatingDirection",
"operator": "matches",
"value": "outbound"
},
{
"type": "dimension",
"dimension": "outboundCampaignId",
"operator": "exists",
"value": null
}
]
},
"views": [],
"metrics": [
"nOutbound",
"nConnected",
"nOutboundAttempted"
]
}
but in the job status it returns me as FAILED status: {"state":"FAILED","errorMessage":"The executed query encountered an unexpected error","submissionDate":"2023-10-27T17:05:18.568Z"} I have reviewed the structure of the query, and I see no problems. Thank you in advance for your help.
Greetings. Julio Segil
Eos_Rios | 2023-10-27 20:31:08 UTC | #2
Failed is usually a problem with the service not you, open a customer care case if it persists.
SimonBrown | 2023-10-28 01:22:50 UTC | #3
Not at work PC but sure you do not need value key on an exists operator. Would hope the back end ignores, but may be worth removing the "value": null
system | 2023-11-27 01:23:24 UTC | #4
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
This post was migrated from the old Developer Forum.
ref: 22791