Resource has expired
For the complete documentation index, see llms.txt. For a full content snapshot, see llms-full.txt. Append .md to any kestra.io/docs/* URL for plain Markdown.

The resource existed, but its lifetime has passed.

  • HTTP status — 410 Gone
  • type — https://kestra.io/docs/api-reference/problems/resource-expired

When you get it

  • A KV Store value is read after its TTL has elapsed.

Example response

A response reporting this problem:

{
  "type": "https://kestra.io/docs/api-reference/problems/resource-expired",
  "title": "Resource has expired",
  "status": 410,
  "detail": "The requested value has expired",
  "instance": "/api/v1/main/namespaces/company.team/kv/my-key"
}

How to handle it

Write the value again rather than retrying the read. The expired entry is deleted as part of the read that reports it, so reading the same key again reports not-found: this response is the one chance to tell an expired value apart from a key that was never set.

For the members every problem document carries, see Problem Details.

Was this page helpful?