Prolong request lock
PUT/v2/request-queues/:queueId/requests/:requestId/lock
Prolongs request lock. The request lock can be prolonged only by the client that has locked it using Get and lock head operation.
Request
Path Parameters
Queue ID or username~queue-name.
WkzbQMuFYuamGv3YFRequest ID.
Example:xpsmkDlspokDSmklSQuery Parameters
How long the requests will be locked for (in seconds).
Example:60A unique identifier of the client accessing the request queue. It must be a string between 1 and 32 characters long. This identifier is used for locking and unlocking requests. You can delete or prolong the lock only for requests that were locked by the same client key or from the same Actor run.
Example:client-abcDetermines if request should be added to the head of the queue or to the end after lock expires.
Example:falseStatus 200
Response Headers
{
"data": {
"lockExpiresAt": "2022-01-01T00:00:00.000Z"
}
}
Schema
data object required
Information about a request lock.
- lockExpiresAt string<date-time> required
The timestamp when the lock expires.
Example:2022-01-01T00:00:00.000Z
- lockExpiresAt string<date-time> required
Status 400
Bad request - invalid input parameters or request body.
{
"error": {
"type": "invalid-input",
"message": "Invalid input: The request body contains invalid data."
}
}
Schema
error object required
- type string requiredExample:
run-failed - message string requiredExample:
Actor run did not succeed (run ID: 55uatRrZib4xbZs, status: FAILED)
- type string requiredExample:
Status 404
Not found - the requested resource was not found.
{
"error": {
"type": "record-not-found",
"message": "Request Queue was not found"
}
}
Schema
error object
- type string
Possible values: [
record-not-found] - message stringExample:
Request Queue was not found
- type string