Long Running Requests Return no Progress Update - DSS C# SDK

alex.smith · June 2021

I have a question around the extractwithnotes async call. When running short requests I have no issue seeing the progress of the job on the callback method however when there is a larger request there is no progress or status update (as far as I can tell). The application awaits the aysnc result but it never actually arrives, even if left overnight.

Is there some step I am missing when handling the long running requests? based on the examples I am seemingly handling this in the right manner but something isn't quite right.

Snap shot of calling code:

var progress = new Progress<HttpAsyncStatus>(Handler);

var job = await ExtractionsContext.ExtractWithNotesAsync(extractionRequest, new CancellationToken(false), progress);

Any advice would be appreciated as the examples aren't overly clear on this matter.

Gurpreet · June 2021

Hi @alex.smith,

The server returns a HTTP-202 Accepted response for async calls. Upon investigating the HTTP response, I see that the progress header is not populated. It might be a bug or an incomplete feature in the DSS service. I would raise a service ticket with product, on your behalf.

HTTP/1.1 202 Accepted
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Location: https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractRawResult(ExtractionId='0x07969d71f57cba22')
Server: Microsoft-IIS/10.0
Status: InProgress
Progress: 
X-Request-Execution-Correlation-Id: CiD/9011672/AAAAAA.07969c75cf3cba20/RA
X-App-Id: Custom.RestApi
X-App-Version: 14.5.72.64
Date: Thu, 10 Jun 2021 13:11:33 GMT
Content-Length: 0

Gurpreet · June 2021

Hi @alex.smith,

I have raised a ticket #09972123 for you. You should directly receive the updates from the DSS support team in email.

alex.smith · June 2021

https://community.developers.refinitiv.com/discussion/comment/79395#Comment_79395

If i'm using the C# SDK does the 202 get returned in some way that I can interrogate it? Also aside from the progress feature being empty, when waiting for a long running request I get no timeout or error even if the request has been running for more than 3 hours. Does the session on the DSS side timeout and not return anything? Just trying to work out a way of handling the long running requests thanks

Gurpreet · June 2021

https://community.developers.refinitiv.com/discussion/comment/79378#Comment_79378

No. 202 is handled by the SDK and not visible to application. The session does not get timed out - you just have to wait longer. You can try to use a intercepting-proxy like Fiddler to capture the HTTP interaction between the server and SDK.