View Categories

Outbound Call activity (Async) is not getting posted

1 min read

Issue:

Outbound call activity is not getting posted and we see the async api request of the outbound call activity is getting failed with the below error response. 
{
    “RequestId”“f560aec8-bdcf-43b2-a050-ad35d200cc9e”,
    “TaskStatus”: {
        “TaskType”“Telephony-LogCall”,
        “Status”“FAILURE”,
        “StatusReason”“Request was attempted but did not succeed. Please check the message”,
        “TaskCurrentStep”null,
        “TaskLastStep”“In-Process-Queue”,
        “RequestBody”“{“DomainId”:”c50e4371-c834-4e62-b57f-133a0a629557″,”SourceNumber”:”intalk”,”DestinationNumber”:”8447810144″,”DisplayNumber”:”8447810144″,”StartTime”:”2023-11-15 13:36:35″,”EndTime”:”2023-11-15 13:43:56″,”CallDuration”:419,”CallNotes”:null,”Status”:”Answered”,”ResourceURL”:”https://ms2byjus1.intalk.io/recordings/ho.byjus1.intalk.io/archive/2023/Nov/15/20231115133635_8447810144.mp3″,”Direction”:”Outbound”,”CallSessionId”:”52bea522-ebb6-4dec-8e09-820d5ac0dce1″,”LeadId”:”b44113e7-eee6-4046-99e2-d1c1da794dc7″,”mx_Custom_10″:”deepak.kumar%40byjus.com”,”mx_Custom_11″:”manual”}”,
        “Message”“{“Status”:”Failure”,”Message”:”Cannot add or update a child row: a foreign key constraint fails (`byjusk12_mxradon`.`ProspectActivity_Base`, CONSTRAINT `FKC_ProspectActivity_Base_RelatedProspectId` FOREIGN KEY (`RelatedProspectId`) REFERENCES `Prospect_Base` (`ProspectID`) ON DELETE CASCA)”}”
    }
}

Resolution:

Need to validate the below items before triggering the api:

1) Make sure the X-API key is fetched from the same LS account as shown in the below screenshot.

Async API Keys

2) Make sure the call path in the URL is fetched from same LS account.

https://{asynchost}/1/api/telephony/logcallcomplete/2477c2666e04a5122d6e61787c5c55c250/c378b61d-e30c-4c45-a436-f08c4fce1edf

Call log APIs

Note: If the above parameters are of different LS account, then the expected lead will not be present and hence the activity will not get posted resulting in error   “Request was attempted but did not succeed. Please check the message”.


Scroll to Top