Extractions/ExtractWithNotesResult does not honor timeout headers.

While Extractions/Extract* honors wait values passed in the Prefer header, Extractions/Extract*Result always lingers for 30 seconds.

We use a serverless architecture for requesting extractions, and we're billed per second of runtime. I would prefer not to have instances alive and waiting for no reason.

NOTE: I am aware of the recommended polling interval of 30 seconds and have no desire to poll more aggressively. I'm actually quite happy to poll even less frequently.

REQUEST EXAMPLE:

GET https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractWithNotesResult(ExtractionId=&#39;<REDACTED>&#39;)
Prefer: respond-async; wait=1
Content-Type: application/json
Authorization: Token <REDACTED>
User-Agent: IntelliJ HTTP Client/IntelliJ IDEA 2024.1.4
Accept-Encoding: br, deflate, gzip, x-gzip
Accept: */*
content-length: 0

###

RESPONSE EXAMPLE:

GET https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractWithNotesResult(ExtractionId=&#39;<REDACTED>&#39;)

HTTP/1.1 202 Accepted
Cache-Control: no-cache
Pragma: no-cache
Expires: -1
Location: https://selectapi.datascope.refinitiv.com/RestApi/v1/Extractions/ExtractWithNotesResult(ExtractionId=&#39;<REDACTED>&#39;)
Server: Microsoft-IIS/10.0
BeginRequestTime: 19:25:33.1955755
BeginRequestDate: 2024-06-25
Status: InProgress
Progress:
X-Request-Execution-Correlation-Id: <REDACTED>
X-App-Id: Custom.RestApi
X-App-Version: 18.1.112.64
CPUUtilization: 18.98858
RequestsPerSec: 0
W3WP-PrivateBytes: 1882704
Date: Tue, 25 Jun 2024 19:26:03 GMT
Content-Length: 0



Response code: 202 (Accepted); Time: 30575ms (30 s 575 ms); Content length: 0 bytes (0 B)

Find more posts tagged with

asynchronous

dss-rest-api

on-demand-extraction

time-out

#technology

#product

Accepted answers

Jirapongse

@fiorella.segura

The behavior is inconsistent.

The case owner should contact the development team to confirm this inconsistent behavior because the following header works with the Extractions/ExtractWithNotes endpoint.

Prefer: respond-async; wait=1

However, it doesn't work with the Extractions/ExtractWithNotesResult(ExtractionId='<REDACTED>') endpoint.

The product team should confirm if this is an expected behavior.

All comments

Jirapongse

@thewildllama

Thank you for reaching out to us.

Please check the answer on this discussion.

You can contact the DSS support team directly via MyAccount to confirm this behavior.

fiorella.segura

Hi @Jirapongse, the support team checked this over case 13659306 and advised to ask you guys over here because the User Guide for TH instructs the same as you highlighted in the other discussion that you are referencing, which sadly confirms the system won't allow that to be less than 30 seconds. If you happen to have any other recommendations for what the client is trying to achieve, please let us know. Thanks!

Jirapongse

@fiorella.segura

The behavior is inconsistent.

The case owner should contact the development team to confirm this inconsistent behavior because the following header works with the Extractions/ExtractWithNotes endpoint.

Prefer: respond-async; wait=1

However, it doesn't work with the Extractions/ExtractWithNotesResult(ExtractionId='<REDACTED>') endpoint.

The product team should confirm if this is an expected behavior.

EXPLORE OUR SITES