Skip to content

iterate_keys defaults to the long timeout while list_keys uses medium #1173

Closed
Bug
#1181
Closed
iterate_keys defaults to the long timeout while list_keys uses medium#1173
Bug
#1181
Assignees
vdusek
Labels
t-toolingIssues with this label are in the ownership of the tooling team.

Description

@vdusek
vdusek
opened on Oct 30, 2026

KeyValueStoreClient.list_keys defaults to timeout='medium' (key_value_store.py#L136-L144), but iterate_keys, which sends the same request page by page, defaults to 'long' (#L179-L188, async #L615-L624). Every other list/iterate pair in the client uses the same tier for both. The JS client uses 'medium' for every page of listKeys (key_value_store.ts#L206-L212).

Expected behavior

iterate_keys defaults to 'medium' in both the sync and async client.

✍️ Drafted by Claude Code

Activity

  1. vdusek
    added
    bugSomething isn't working.
    low priorityLow priority issues to be done eventually.
    t-toolingIssues with this label are in the ownership of the tooling team.
    on Oct 30, 2026
  2. vdusek
    added the
    Bug
    issue type on Oct 30, 2026
  3. vdusek
    removed
    bugSomething isn't working.
    low priorityLow priority issues to be done eventually.
    on Oct 30, 2026
  4. vdusek
    added a commit that references this issue on Oct 30, 2026

    fix: align key iteration timeout with key listing (#1181)

    6097ad3
  5. vdusek
    self-assigned this
    on Oct 30, 2026
  6. apify-service-account
    closed this as completedon Oct 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

t-toolingIssues with this label are in the ownership of the tooling team.

Type

Bug

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions