From bb9deb64dd2e4609102e9ad9284d6b4c9f6fd634 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20=28Honza=29=20Jir=C3=A1=C5=88?= Date: Mon, 21 Sep 2026 11:08:39 +0200 Subject: [PATCH 1/4] docs: update published task limits to 10 per Actor and 100 per account Part of apify/apify-core#30452 Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01WRi5mRuTVkbQjt5JsrxRFw --- .../paths/actor-tasks/actor-tasks@{actorTaskId}.yaml | 6 +++--- sources/platform/actors/publishing/publish-task.mdx | 2 +- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml b/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml index 0343cd5cb5..48c4984271 100644 --- a/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml +++ b/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml @@ -57,9 +57,9 @@ put: write permission to the task's Actor. To publish a task, its Actor must be public, `publicConfig.inputSchemaFields` and - `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, 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. Publishing lists the task among the Actor's examples and makes its input public, so anyone can view and copy it. The landing page itself is shown only while `publicConfig` still diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index 5ac609c2b8..8149667958 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -7,7 +7,7 @@ sidebar_position: 2 [Actor tasks](/actors/running/tasks) are shareable, pre-configured inputs for your Actors. [Publishing a task](#publish-your-tasks) creates a public landing page that shows what it does, what inputs to provide, and what output to expect. Published tasks also appear in your Actor's **Example tasks** tab, which helps users discover your Actor through search engines and AI agents. For monetized Actors, more discoverability means more paid runs. -You can create up to 50 tasks per Actor. +You can publish up to 10 tasks per Actor, and up to 100 tasks across your account. If you need more, contact [support@apify.com](mailto:support@apify.com). ## Prerequisites From 9f7de7d907c7cce294e091e8277a9e4de1540b2b Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20Jir=C3=A1=C5=88?= <50450387+Janjiran@users.noreply.github.com> Date: Tue, 22 Sep 2026 16:17:54 +0200 Subject: [PATCH 2/4] Update sources/platform/actors/publishing/publish-task.mdx Co-authored-by: Edyta <142720610+szaganek@users.noreply.github.com> --- sources/platform/actors/publishing/publish-task.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/platform/actors/publishing/publish-task.mdx b/sources/platform/actors/publishing/publish-task.mdx index 8149667958..3e3c1269ff 100644 --- a/sources/platform/actors/publishing/publish-task.mdx +++ b/sources/platform/actors/publishing/publish-task.mdx @@ -7,7 +7,7 @@ sidebar_position: 2 [Actor tasks](/actors/running/tasks) are shareable, pre-configured inputs for your Actors. [Publishing a task](#publish-your-tasks) creates a public landing page that shows what it does, what inputs to provide, and what output to expect. Published tasks also appear in your Actor's **Example tasks** tab, which helps users discover your Actor through search engines and AI agents. For monetized Actors, more discoverability means more paid runs. -You can publish up to 10 tasks per Actor, and up to 100 tasks across your account. If you need more, contact [support@apify.com](mailto:support@apify.com). +You can publish up to 10 tasks per Actor, and up to 100 tasks across your account. To increase these limits, [contact support](http://apify.com/contact). ## Prerequisites From 6822c2ec04b56ad381f0b1e7e0ffd86e8f9194ca Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20=28Honza=29=20Jir=C3=A1=C5=88?= Date: Tue, 22 Sep 2026 16:19:20 +0200 Subject: [PATCH 3/4] docs: address review on the published task limits 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) Claude-Session: https://claude.ai/code/session_01WRi5mRuTVkbQjt5JsrxRFw --- .../paths/actor-tasks/actor-tasks@{actorTaskId}.yaml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml b/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml index 48c4984271..aec0bb0c03 100644 --- a/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml +++ b/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml @@ -57,9 +57,10 @@ put: write permission to the task's Actor. To publish a task, its Actor must be public, `publicConfig.inputSchemaFields` and - `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. + `publicConfig.datasetView` must be set, and the publishing limits must leave room for it. + By default an Actor can have up to 10 published tasks and an account up to 100; both are + defaults and can be raised per account on request. If the task isn't ready to be published, + the whole update fails and none of it is applied. Publishing lists the task among the Actor's examples and makes its input public, so anyone can view and copy it. The landing page itself is shown only while `publicConfig` still From 3e200b181073aa27ff08712f4f08fcd925e5dfbe Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Jan=20=28Honza=29=20Jir=C3=A1=C5=88?= Date: Wed, 23 Sep 2026 15:04:19 +0200 Subject: [PATCH 4/4] docs: reword the task publishing conditions in the API reference Follows the reviewer's suggested wording: state the limits as "up to", point at the contact form, and spell out that a failed publish leaves every field unchanged, publishing-related or not. Part of apify/apify-core#30452 Co-Authored-By: Claude Opus 5 (1M context) Claude-Session: https://claude.ai/code/session_01WRi5mRuTVkbQjt5JsrxRFw --- .../paths/actor-tasks/actor-tasks@{actorTaskId}.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml b/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml index aec0bb0c03..854f7c46c5 100644 --- a/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml +++ b/apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}.yaml @@ -56,11 +56,11 @@ put: landing page, and `isPublic` publishes or unpublishes the task itself. Both require write permission to the task's Actor. - To publish a task, its Actor must be public, `publicConfig.inputSchemaFields` and - `publicConfig.datasetView` must be set, and the publishing limits must leave room for it. - By default an Actor can have up to 10 published tasks and an account up to 100; both are - defaults and can be raised per account on request. If the task isn't ready to be published, - the whole update fails and none of it is applied. + 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](http://apify.com/contact). + If the task doesn't meet all these conditions, the request fails and no fields are updated, + including those unrelated to publishing. Publishing lists the task among the Actor's examples and makes its input public, so anyone can view and copy it. The landing page itself is shown only while `publicConfig` still