draeder | 2021-04-07 21:37:49 UTC | #1
This is happening in both the API Explorer and in my code.
Using this endpoing /api/v2/telephony/providers/edges/trunks/{trunkId}/metrics in the API Explorer results in:
{ "message": "TrunkStatus not found with id 246bae11-dafd-491d-98a5-8ae34db10548", "code": "general.resource.not.found", "status": 404, "messageWithParams": "{entityType} not found with id {entityId}", "messageParams": { "entityType": "TrunkStatus", "entityId": "246bae11-dafd-491d-98a5-8ae34db10548" }, "contextId": "317c8cd8-eba4-4633-8856-e548f10baba1", "details": [ { "errorCode": "ENTITYNOTFOUND" } ], "errors": [] }
Here is the inin-correlation-id for that API explorer call: 317c8cd8-eba4-4633-8856-e548f10baba1
The trunk certainly exists, and I can confirm in the API explorer with /api/v2/telephony/providers/edges/{edgeId}/trunks:
{ "entities": [ { "id": "246bae11-dafd-491d-98a5-8ae34db10548", . . .
I can further confirm the trunk exists with: /api/v2/telephony/providers/edges/trunks/{trunkId} which returns the trunk by ID
This was working fine in both my code and the API explorer until about 40 minutes ago.
Did something recently change with the Platform API that is causing this issue?
Note: the trunks do appear in Genesys Cloud Admin.
Thanks, Dan
draeder | 2021-04-08 13:57:30 UTC | #3
This seems to be happening intermittently... Is anyone able to take a look?
Thanks, Dan
tim.smith | 2021-04-08 14:04:01 UTC | #4
Please open a case with Genesys Cloud Care to investigate this issue. Missing data cannot be investigated via the forum.
draeder | 2021-04-08 14:16:55 UTC | #5
Will do - Thanks Tim!
system | 2021-05-09 14:16:58 UTC | #6
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: 10532