Exporting outbound dialler contact lists

[Trystan]

Hello,

I using the function here
[SDK Documentation Explorer (genesys.cloud)]

It works for only some of our contact lists. Here is the error I am sometimes receiving when it does not work.

[Error] Exception when calling OutboundApi->post_outbound_contactlist_export: (404)Reason: Not FoundHTTP response headers: HTTPHeaderDict({'Content-Type': 'application/json', 'Content-Length': '389', 'Connection': 'keep-alive', 'Date': 'Thu, 20 Oct 2022 02:05:15 GMT', 'ININ-Correlation-Id': '7374cbb3-36b0-4f98-a9c0-0d294c02f60f', 'Strict-Transport-Security': 'max-age=600; includeSubDomains', 'Cache-Control': 'no-cache, no-store, must-revalidate', 'X-Cache': 'Error from cloudfront', 'Via': '1.1 f1d7bef7d2e148025cea4670117d1f4a.cloudfront.net (CloudFront)', 'X-Amz-Cf-Pop': 'SYD1-C2', 'X-Amz-Cf-Id': 'ymINUxdpwP5pehVGNjD_KYcQ08CWwh6epyKrDg2jD7RQYzIDPIowXg=='})HTTP response body: {"message":"There is no available download URI for contact list {794665b8-918f-43fb-a1b7-7c28c6f75d95} at this time","code":"no.available.list.export.uri","status":404,"messageWithParams":"There is no available download URI for contact list {794665b8-918f-43fb-a1b7-7c28c6f75d95} at this time","messageParams":{},"contextId":"7374cbb3-36b0-4f98-a9c0-0d294c02f60f","details":[],"errors":[]}

Thanks,

Trystan.

[Trystan]

Any thoughts on this error?

I suspect the SDK may not allow time to generate the export files and then fail.

Thanks.

[tim.smith]

The timing for when to call the POST to initiate the export and when to call the GET to get the download URI for it is determined by your application, not the SDK. Exporting contact lists is fast, but is a process that does take an amount of time. Because it is an asynchronous process that can result in a race condition, your application should take measures to handle the error and retry at an interval. The recommended exponential backoff logic for retrying API requests can be found here: https://developer.genesys.cloud/platform/api/rate-limits#retrying-other-responses. If you collect metrics in your app about how long it usually takes for exports to become available, your app could use preemptively sleep for that amount of time to increase the chance of success on the first request. Your retry interval could be refined based on those measurements as well.