Skip to content

docs: fix high and medium inaccuracies in storage, proxy, and other pages#2729

Open
mtrunkat wants to merge 1 commit into
masterfrom
claude/docs-fix-rest-8g4myu
Open

docs: fix high and medium inaccuracies in storage, proxy, and other pages#2729
mtrunkat wants to merge 1 commit into
masterfrom
claude/docs-fix-rest-8g4myu

Conversation

@mtrunkat

@mtrunkat mtrunkat commented Jul 2, 2026

Copy link
Copy Markdown
Member

Corrects high- and medium-severity discrepancies across Storage, Proxy, Console, Monitoring, and Schedules docs, verified against apify-core and apify-proxy.

  • Storage (high): key-value store key limit is 256 characters with a defined character set (not 63); dataset tabulation column limit is 2000 (not 3000).
  • Storage: request-queue rate limits corrected (request-lock 400/s, batch and list-and-lock-head 40/s, others 60/s).
  • Proxy: datacenter rotation picks the oldest IP from a random subset (not all IPs); residential session lifetime is ~30 minutes and provider-specific (not 1 minute); Google SERP num rejects invalid values with 400 rather than silently ignoring; "Own proxies" uses the Input tab.
  • Monitoring: aggregated alert interval is 20 minutes.
  • Schedules: documented the random time offset applied to @hourly/@daily/@weekly/@monthly/@yearly shortcuts.
  • Console: MCP connector button "Add connector"; fixed a broken internal link to Actors in Store.

Generated by Claude Code

…d other pages

- storage/dataset.md: tabulation column limit 3000 -> 2000
- storage/key-value-store.md: key length limit 63 -> 256 chars (+ allowed characters)
- storage/request_queue.md: clarify non-CRUD rate limits (request-lock 400/s, batch and head-lock 40/s, others 60/s)
- monitoring/index.md: aggregated alert interval 15 -> 20 minutes
- schedules.md: document random time offset applied to @hourly/@daily/@weekly/@monthly/@Yearly shortcuts
- proxy/datacenter_proxy.md: rotation selects oldest IP from a random subset, not all IPs
- proxy/google_serp_proxy.md: invalid num values are rejected with 400, not silently ignored
- proxy/index.md: residential session lifetime 1 minute -> ~30 minutes (provider-specific)
- proxy/residential_proxy.md: session persistence ~30 minutes (provider-set), reworked keep-alive tip
- proxy/your_own_proxies.md: tab labeled Input (not "Input and options"); proxy section is schema-defined
- console/settings.md: MCP connector button label "Create new connector" -> "Add connector"
- console/store.md: fix Actors in Store link to served route /platform/actors/running/actors-in-store
Copilot AI review requested due to automatic review settings July 2, 2026 20:01
@apify-service-account

apify-service-account commented Jul 2, 2026

Copy link
Copy Markdown
Contributor

✅ Preview for this PR (commit 80bcd4d) is ready at https://pr-2729.preview.docs.apify.com (see action run).

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR updates Apify platform documentation to correct several high- and medium-severity factual inaccuracies across Storage, Proxy, Monitoring, Schedules, and Console pages, aligning the docs with current platform behavior and limits.

Changes:

  • Corrected Storage limits and rate limits (request queue rate limiting, key-value store key constraints, dataset tabulation column limits).
  • Updated Proxy behavior details (datacenter rotation selection, residential session lifetime semantics, Google SERP num handling, Console UI instructions for own proxies).
  • Clarified operational/UI behavior (Schedules shortcut random offsets, Monitoring aggregated alert interval, Console Store link + MCP connector button label).

Reviewed changes

Copilot reviewed 12 out of 12 changed files in this pull request and generated 3 comments.

Show a summary per file
File Description
sources/platform/storage/request_queue.md Documents per-endpoint request queue API rate limits.
sources/platform/storage/key_value_store.md Updates key length limit and documents allowed key characters.
sources/platform/storage/dataset.md Corrects the maximum tabulation column limit for dataset exports.
sources/platform/schedules.md Adds documentation for random offsets applied to @hourly/@daily/etc. shortcuts.
sources/platform/proxy/your_own_proxies.md Updates Console UI guidance for configuring custom proxies.
sources/platform/proxy/residential_proxy.md Corrects residential session lifetime and session reuse guidance.
sources/platform/proxy/index.md Updates proxy session lifetime summary for residential proxies.
sources/platform/proxy/google_serp_proxy.md Clarifies deprecated num behavior and error handling.
sources/platform/proxy/datacenter_proxy.md Refines explanation of datacenter IP rotation selection strategy.
sources/platform/monitoring/index.md Updates aggregated alert interval from 15 to 20 minutes.
sources/platform/console/store.md Fixes internal link target for “Actors in Store”.
sources/platform/console/settings.md Updates MCP connectors button label to “Add connector”.

## Limits

- The maximum length for a key in a key-value store is 63 characters.
- The maximum length for a key in a key-value store is 256 characters. Keys may only contain the following characters: `a-zA-Z0-9!-_.'()`.
## Limits

- Data storage formats that use tabulation (like HTML, CSV, and EXCEL) are limited to a maximum of _3000_ columns. Data exceeding this limit will not be retrieved.
- Data storage formats that use tabulation (like HTML, CSV, and EXCEL) are limited to a maximum of _2000_ columns. Data exceeding this limit will not be retrieved.
[delete](/api/v2/request-queue-request-delete))
operation requests are limited to _400 requests per second_ per request queue. This helps protect Apify servers from being overloaded.

Request-lock operations ([prolong](/api/v2/request-queue-request-lock-put) and [delete](/api/v2/request-queue-request-lock-delete) a lock) are also limited to _400 requests per second_ per request queue.
@mtrunkat mtrunkat added the adhoc Ad-hoc unplanned task added during the sprint. label Jul 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

adhoc Ad-hoc unplanned task added during the sprint.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants