Conversation
Part of apify/apify-core#30452 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WRi5mRuTVkbQjt5JsrxRFw
|
✅ Preview for this PR (commit |
| `publicConfig.datasetView` must be set, the Actor must have fewer than 10 published | ||
| tasks, and the task owner's account must have fewer than 100 published tasks. If the task | ||
| isn't ready to be published, the whole update fails and none of it is applied. |
There was a problem hiding this comment.
In the file below, it says up to x tasks which is technically correct. Saying fewer than x tasks is incorrect. Also, it is worth mentioning that those are only the default limits, each account can have them overridden to a custom number.
Co-authored-by: Edyta <142720610+szaganek@users.noreply.github.com>
Say "up to 10 published tasks" instead of "fewer than", note that both numbers are defaults that can be raised per account, and point at the contact form rather than the support mailbox. Part of apify/apify-core#30452 Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01WRi5mRuTVkbQjt5JsrxRFw
szaganek
left a comment
szaganek
left a comment
There was a problem hiding this comment.
The entire paragraph is very fluffy now, I left a suggestion. Approving in advance tho :)
| `publicConfig.datasetView` must be set, and the Actor must have fewer than 50 published | ||
| tasks. If the task isn't ready to be published, the whole update fails and none of it | ||
| is applied. | ||
| `publicConfig.datasetView` must be set, and the publishing limits must leave room for it. |
There was a problem hiding this comment.
I'd go with something like this:
To publish a task, its Actor must be public and both publicConfig.inputSchemaFields and publicConfig.datasetView must be set. Note that an Actor can have up to 10 published tasks and your account up to 100. To increase these limits, contact support. If the task doesn't meet all these conditions, the request fails and no fields are updated, including those unrelated to publishing.
This branch has not been deployed
4 participants
Part of apify/apify-core#30452.
The platform limits change in apify/apify-core#30442: 10 published tasks per Actor (was 50) and a new limit of 100 published tasks per account.
Updated:
publish-task.mdxintro: the stale "create up to 50 tasks per Actor" line now states both publishing limits and points to support for a raiseactor-tasks@{actorTaskId}.yaml: the Update task endpoint description lists both limitsMerge only after the apify-core change ships.