From c5dadd6aceece851d7be965faee96ec6d13c3624 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 30 Sep 2026 10:48:02 +0200 Subject: [PATCH 01/10] fix: correct the under-maintenance test threshold The QA daemon flags an Actor when most of three days' test runs fail on one build, not after three consecutive failing days. Also fixes the testing links in actor-status and the stale contact-support advice in the Academy. --- .../build-and-publish/apify-store-basics/how_store_works.md | 4 ++-- sources/platform/actors/publishing/actor-status.mdx | 4 ++-- sources/platform/actors/publishing/testing.mdx | 3 +-- 3 files changed, 5 insertions(+), 6 deletions(-) diff --git a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md index 7f00f6b4df..5dbec94e5b 100644 --- a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md +++ b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md @@ -52,9 +52,9 @@ For details, see [Actor developers](/actors/running/store/actor-developers). It's essential to test your Actors and make sure they work as intended. That's why Apify does it on our side as much as you should do it on yours. -Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check _if an Actor can successfully run with its default input within 5 minutes_. If an Actor fails for three consecutive days, it’s labeled under maintenance, and the developer is notified. Continuous failures for another 28 days lead to deprecation. +Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check _if an Actor can successfully run with its default input within 5 minutes_. If an Actor fails most of its test runs over three days, Apify labels it under maintenance and notifies the developer. Continuous failures for another 28 days lead to deprecation. -To restore an Actor's health, developers should fix and rebuild it. The testing system will automatically recognize the changes within 24 hours. If your Actor requires longer run times or authentication, contact support to explain why it should be excluded from tests. For more control, you can implement your own tests using the Actor Testing tool available on Apify Store. +To restore an Actor's health, developers should fix and rebuild it. The testing system will automatically recognize the changes within 24 hours. If your Actor can't pass the tests, for example because it needs more than 5 minutes, you can request to skip them. For details, see [Actor testing](/actors/publishing/test#what-if-my-actor-cannot-comply-with-the-test-logic). For more control, you can implement your own tests using the Actor Testing tool available on Apify Store. ### Actor metrics and reliability score diff --git a/sources/platform/actors/publishing/actor-status.mdx b/sources/platform/actors/publishing/actor-status.mdx index db450c6c96..aead0887d3 100644 --- a/sources/platform/actors/publishing/actor-status.mdx +++ b/sources/platform/actors/publishing/actor-status.mdx @@ -41,7 +41,7 @@ To let users know that the Actor might temporarily not work as expected, use the 1. _(Optional)_ In the **Under maintenance message** field, add an additional explanation. 1. Select **Save**. -Note that the **Under maintenance** status makes your Actor rank lower in search results. It's also automatically set when your Actor fails the [automated testing](../development/automated_tests.md) process. +Note that the **Under maintenance** status makes your Actor rank lower in search results. It's also automatically set when your Actor fails the [automated testing](./testing.mdx) process. ### Mark Actor as deprecated @@ -53,4 +53,4 @@ To let your users know that the Actor is no longer being developed, use the **De Don't delete the Actor as it might break the existing integrations. -Note that the deprecated Actors aren't searchable in Apify Store. The **Deprecated** status is also automatically set when your Actor fails the [automated testing](../development/automated_tests.md) process for 30 days. +Note that the deprecated Actors aren't searchable in Apify Store. The **Deprecated** status is also automatically set when your Actor fails the [automated testing](./testing.mdx) process for 30 days. diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx index 7017f5b367..ffbfb4a861 100644 --- a/sources/platform/actors/publishing/testing.mdx +++ b/sources/platform/actors/publishing/testing.mdx @@ -18,8 +18,7 @@ and expects it to finish with a **Succeeded** status and non-empty default datas ![Actor page](./images/actor-test.webp) -If the Actor fails to complete successful runs for three consecutive days, the developer will be notified, -and the Actor will be labeled `under maintenance` until it is fixed. After another 14 days of failing runs, you will receive another notification. Finally, if the runs continue to fail after yet another 14 days, the Actor will be `deprecated`. +If more than half of the daily test runs in the last three days fail, Apify notifies you and labels the Actor `under maintenance` until it's fixed. All test runs in those three days must use the same build, so a new build restarts the count. After another 14 days of failing runs, you get another notification. If the runs still fail 14 days after that, Apify marks the Actor as `deprecated`. ## How can I make my Actor healthy again From a19b728139c9b1f8c4d0a4b40fcbf28980065f97 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 30 Sep 2026 10:48:02 +0200 Subject: [PATCH 02/10] docs: add troubleshooting steps for Actors under maintenance Ports the Help Center article "Troubleshooting an Actor marked Under maintenance", grounded against the test runner and notification templates. --- .../platform/actors/publishing/testing.mdx | 37 ++++++++++++++++++- 1 file changed, 35 insertions(+), 2 deletions(-) diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx index ffbfb4a861..b622ec3e3b 100644 --- a/sources/platform/actors/publishing/testing.mdx +++ b/sources/platform/actors/publishing/testing.mdx @@ -20,6 +20,28 @@ and expects it to finish with a **Succeeded** status and non-empty default datas If more than half of the daily test runs in the last three days fail, Apify notifies you and labels the Actor `under maintenance` until it's fixed. All test runs in those three days must use the same build, so a new build restarts the count. After another 14 days of failing runs, you get another notification. If the runs still fail 14 days after that, Apify marks the Actor as `deprecated`. +## Find out why the test failed + +When Apify labels your Actor `under maintenance`, you get a notification in Apify Console and by email. What it says depends on whether the test could start the Actor. + +### The test couldn't start the Actor + +This usually means a problem with the input schema. The test builds its input from the schema's `prefill` values. Every required field needs a `prefill` or `default` value, and every value must pass the schema's validation. For example, a `prefill` of `3` fails for a field with `"maximum": 2`. + +To see the input the test uses: + +1. In Apify Console, open your Actor. +1. Go to **Source** > **Input**. +1. Select **Restore example input**. The form loads the values from the input schema and shows an error next to any value that fails validation. + +Fix the input schema, then rebuild the Actor. + +### The test run failed + +The notification links to one of the failed test runs. Check its log for the cause. + +If the run timed out, make the test input smaller. `prefill` or `default` values that return a few results are enough, so the run finishes within the 5-minute limit. + ## How can I make my Actor healthy again The best course of action is to fix the Actor and rebuild it. The automatic testing system will pick this up within 24 hours @@ -28,8 +50,19 @@ passes the majority of test runs in the next 7 days, it will be marked as health ## What if my Actor cannot comply with the test logic -Actors that require some sort of authentication will always fail the tests despite being fully functional. Also, some Actors inherently run for longer than 5 minutes. -If that's the case with your Actor, [contact support](http://apify.com/contact) and explain your specific use case that justifies why the Actor should be excluded from the automated tests. +Some Actors aren't tested automatically: + +- Actors with [Actor Standby](../running/actor_standby.md) enabled +- Actors in the MCP servers category +- Actors with a required secret input, or a required API token or key without a `prefill` value + +If your Actor can't pass the test for another reason, such as needing more than 5 minutes to finish, request to skip the tests: + +1. In the under-maintenance notification, open the form link. It opens the **Request to skip Actor checks** dialog in your Actor's **Settings** tab. +1. Explain why your Actor should skip the tests. +1. Select **Send request**. + +Apify approves requests only in exceptional cases. You can also [contact support](https://apify.com/contact). ## Advanced Actor testing From 3bbba46502e3585923da381b5986fc3ec6d14638 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 30 Sep 2026 10:48:02 +0200 Subject: [PATCH 03/10] docs: explain what to do when an Actor you use is under maintenance Ports the Help Center article "What to do when your Actor comes under maintenance" to the Store page, where Actor users look. --- sources/platform/actors/publishing/testing.mdx | 2 ++ sources/platform/actors/running/store/index.md | 12 ++++++++++++ 2 files changed, 14 insertions(+) diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx index b622ec3e3b..a2b30c7999 100644 --- a/sources/platform/actors/publishing/testing.mdx +++ b/sources/platform/actors/publishing/testing.mdx @@ -11,6 +11,8 @@ sidebar_position: 3 We want to make sure that all Actors in Apify Store are top-notch, or at least as top-notch as they can be. Since there are many of them, we have an automated testing procedure in place that tests all Actors daily. This helps us to flag Actors that temporarily don't work as expected `under maintenance`, and to automatically `deprecate` Actors that have been broken for more than a month. +If you use an Actor that's under maintenance, see [Actors under maintenance](/actors/running/actors-in-store#actors-under-maintenance). + ## How we test The test runs the Actor with its default input (defined by the [**prefill**](https://docs.apify.com/actors/development/actor-definition/input-schema/specification/v1#prefill-vs-default-vs-required) option in the input schema file) diff --git a/sources/platform/actors/running/store/index.md b/sources/platform/actors/running/store/index.md index bebc7e9b04..e242f1ae38 100644 --- a/sources/platform/actors/running/store/index.md +++ b/sources/platform/actors/running/store/index.md @@ -97,6 +97,18 @@ To see a breakdown of rental charges, go to the **Actors** tab within the **Curr ![Rental Actors billing in Apify Console](../images/store/billing-paid-actors.png) +## Actors under maintenance + +An Actor gets the **Under maintenance** label when it fails Apify's [automated tests](/actors/publishing/test), or when its developer sets it. Its page then shows the **This Actor is under maintenance** banner, sometimes with a message from the developer. Its runs can fail or return incomplete results. + +If an Actor you use is under maintenance: + +- Run it with a small input, such as a few pages, and check the results. +- On the Actor's **Issues** tab, look for an issue that describes your problem. If there isn't one, create one to ask the developer. For details, see [Report issues with Actors](#report-issues-with-actors). +- To find a replacement, select **Show similar Actors** in the banner, or search [Apify Store](https://apify.com/store). + +Actors under maintenance rank lower in Apify Store. If an Actor keeps failing its tests, Apify deprecates it after about a month. + ## Report issues with Actors Each Actor has an **Issues** tab in Apify Console. There, you can open an issue (ticket) and chat with the Actor's author, platform admins, From f6a55c331311f6caf8da8f66ab8f8bd3049c9591 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 21 Oct 2026 22:33:06 +0200 Subject: [PATCH 04/10] Apply batched suggestions from code review Co-authored-by: Edyta <142720610+szaganek@users.noreply.github.com> --- .../build-and-publish/apify-store-basics/how_store_works.md | 4 ++-- sources/platform/actors/publishing/testing.mdx | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md index 5dbec94e5b..94187b1c3d 100644 --- a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md +++ b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md @@ -52,9 +52,9 @@ For details, see [Actor developers](/actors/running/store/actor-developers). It's essential to test your Actors and make sure they work as intended. That's why Apify does it on our side as much as you should do it on yours. -Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check _if an Actor can successfully run with its default input within 5 minutes_. If an Actor fails most of its test runs over three days, Apify labels it under maintenance and notifies the developer. Continuous failures for another 28 days lead to deprecation. +Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check if an Actor can successfully run with its default input within 5 minutes. If an Actor fails most of its test runs over three days, Apify labels it under maintenance and notifies the developer. Continuous failures for another 28 days lead to deprecation. -To restore an Actor's health, developers should fix and rebuild it. The testing system will automatically recognize the changes within 24 hours. If your Actor can't pass the tests, for example because it needs more than 5 minutes, you can request to skip them. For details, see [Actor testing](/actors/publishing/test#what-if-my-actor-cannot-comply-with-the-test-logic). For more control, you can implement your own tests using the Actor Testing tool available on Apify Store. +To restore an Actor's health, developers should fix and rebuild the Actor. The testing system will automatically recognize the changes within 24 hours. If your Actor can't pass the tests, for example because it needs more than 5 minutes to finish the run, you can request to skip the tests. For details, see [Actor testing](/actors/publishing/test#what-if-my-actor-cannot-comply-with-the-test-logic). For more control, you can implement your own tests using the Actor Testing tool available on Apify Store. ### Actor metrics and reliability score diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx index a2b30c7999..4c0e333eb0 100644 --- a/sources/platform/actors/publishing/testing.mdx +++ b/sources/platform/actors/publishing/testing.mdx @@ -52,7 +52,7 @@ passes the majority of test runs in the next 7 days, it will be marked as health ## What if my Actor cannot comply with the test logic -Some Actors aren't tested automatically: +The following Actors aren't tested automatically: - Actors with [Actor Standby](../running/actor_standby.md) enabled - Actors in the MCP servers category From 08400ec62fc2bb92d0a894966f2798bb79dfbc58 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 21 Oct 2026 22:45:57 +0200 Subject: [PATCH 05/10] docs: address review feedback on the under-maintenance pages Grounded in the test runner: the test input comes from prefill only, and secrets and un-prefilled tokens are two separate exclusions. The skip-tests dialog opens only from the notification link, so the Settings hint goes. --- .../apify-store-basics/how_store_works.md | 4 ++-- .../platform/actors/publishing/testing.mdx | 23 ++++++++++--------- .../platform/actors/running/store/index.md | 6 ++--- 3 files changed, 17 insertions(+), 16 deletions(-) diff --git a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md index 94187b1c3d..a01922d6c4 100644 --- a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md +++ b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md @@ -52,9 +52,9 @@ For details, see [Actor developers](/actors/running/store/actor-developers). It's essential to test your Actors and make sure they work as intended. That's why Apify does it on our side as much as you should do it on yours. -Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check if an Actor can successfully run with its default input within 5 minutes. If an Actor fails most of its test runs over three days, Apify labels it under maintenance and notifies the developer. Continuous failures for another 28 days lead to deprecation. +Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check whether an Actor's run with its default input succeeds within 5 minutes. If an Actor fails most of its test runs over three days, Apify labels it under maintenance and notifies the developer. If the Actor keeps failing for another 28 days, Apify deprecates it. -To restore an Actor's health, developers should fix and rebuild the Actor. The testing system will automatically recognize the changes within 24 hours. If your Actor can't pass the tests, for example because it needs more than 5 minutes to finish the run, you can request to skip the tests. For details, see [Actor testing](/actors/publishing/test#what-if-my-actor-cannot-comply-with-the-test-logic). For more control, you can implement your own tests using the Actor Testing tool available on Apify Store. +To restore your Actor's health, fix and rebuild it. The tests use the new build within 24 hours. If your Actor can't pass the tests, for example because it needs more than 5 minutes to finish, you can request to skip the tests. For details, see [Actor testing](/actors/publishing/test#what-if-my-actor-cannot-comply-with-the-test-logic). For more control, you can write your own tests with the [Actor Testing](https://apify.com/pocesar/actor-testing) tool from Apify Store. ### Actor metrics and reliability score diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx index 4c0e333eb0..b93349ea01 100644 --- a/sources/platform/actors/publishing/testing.mdx +++ b/sources/platform/actors/publishing/testing.mdx @@ -20,15 +20,15 @@ and expects it to finish with a **Succeeded** status and non-empty default datas ![Actor page](./images/actor-test.webp) -If more than half of the daily test runs in the last three days fail, Apify notifies you and labels the Actor `under maintenance` until it's fixed. All test runs in those three days must use the same build, so a new build restarts the count. After another 14 days of failing runs, you get another notification. If the runs still fail 14 days after that, Apify marks the Actor as `deprecated`. +If more than half of the daily test runs in the last three days fail, Apify notifies you and labels the Actor `under maintenance` until you fix it. All test runs in those three days must use the same build, so a new build restarts the count. After another 14 days of failing runs, you get another notification. If the runs still fail 14 days after that, Apify marks the Actor as `deprecated`. ## Find out why the test failed -When Apify labels your Actor `under maintenance`, you get a notification in Apify Console and by email. What it says depends on whether the test could start the Actor. +When Apify labels your Actor `under maintenance`, you get a notification in Apify Console and by email. The notification tells you whether the test could start the Actor. The fix differs for each case. ### The test couldn't start the Actor -This usually means a problem with the input schema. The test builds its input from the schema's `prefill` values. Every required field needs a `prefill` or `default` value, and every value must pass the schema's validation. For example, a `prefill` of `3` fails for a field with `"maximum": 2`. +If the test couldn't start the Actor, the cause is usually a problem with the input schema. The test builds its input from the schema's `prefill` values. Every required field needs a `prefill` value, and every value must pass the schema's validation. For example, a `prefill` of `3` fails for a field with `"maximum": 2`. To see the input the test uses: @@ -36,13 +36,13 @@ To see the input the test uses: 1. Go to **Source** > **Input**. 1. Select **Restore example input**. The form loads the values from the input schema and shows an error next to any value that fails validation. -Fix the input schema, then rebuild the Actor. +Fix the input schema, then rebuild the Actor, because the test reads the schema from the build. ### The test run failed -The notification links to one of the failed test runs. Check its log for the cause. +When a test run fails, the notification links to it. Check its log for the cause. -If the run timed out, make the test input smaller. `prefill` or `default` values that return a few results are enough, so the run finishes within the 5-minute limit. +If the run timed out, make the test input smaller. Choose `prefill` values that return only a few results, so the run finishes within the 5-minute limit. ## How can I make my Actor healthy again @@ -52,19 +52,20 @@ passes the majority of test runs in the next 7 days, it will be marked as health ## What if my Actor cannot comply with the test logic -The following Actors aren't tested automatically: +The automated test skips these Actors: - Actors with [Actor Standby](../running/actor_standby.md) enabled - Actors in the MCP servers category -- Actors with a required secret input, or a required API token or key without a `prefill` value +- Actors with a required secret input +- Actors with a required token or key input that has no `prefill` value If your Actor can't pass the test for another reason, such as needing more than 5 minutes to finish, request to skip the tests: -1. In the under-maintenance notification, open the form link. It opens the **Request to skip Actor checks** dialog in your Actor's **Settings** tab. -1. Explain why your Actor should skip the tests. +1. In the under-maintenance notification, open the form link. +1. In the **Request to skip Actor checks** dialog, explain why your Actor should skip the tests. 1. Select **Send request**. -Apify approves requests only in exceptional cases. You can also [contact support](https://apify.com/contact). +Apify approves requests only in exceptional cases. ## Advanced Actor testing diff --git a/sources/platform/actors/running/store/index.md b/sources/platform/actors/running/store/index.md index e242f1ae38..b9a6b02f64 100644 --- a/sources/platform/actors/running/store/index.md +++ b/sources/platform/actors/running/store/index.md @@ -99,12 +99,12 @@ To see a breakdown of rental charges, go to the **Actors** tab within the **Curr ## Actors under maintenance -An Actor gets the **Under maintenance** label when it fails Apify's [automated tests](/actors/publishing/test), or when its developer sets it. Its page then shows the **This Actor is under maintenance** banner, sometimes with a message from the developer. Its runs can fail or return incomplete results. +An Actor gets the **Under maintenance** label when it fails Apify's [automated tests](/actors/publishing/test), or when its developer sets it. Its page then shows the **This Actor is under maintenance** banner, sometimes with a message from the developer. If you run it, the run can fail or return incomplete results. If an Actor you use is under maintenance: -- Run it with a small input, such as a few pages, and check the results. -- On the Actor's **Issues** tab, look for an issue that describes your problem. If there isn't one, create one to ask the developer. For details, see [Report issues with Actors](#report-issues-with-actors). +- Run it with a small input and check the results. +- On the Actor's **Issues** tab, look for an issue that describes your problem. If there isn't one, create one to ask the developer. - To find a replacement, select **Show similar Actors** in the banner, or search [Apify Store](https://apify.com/store). Actors under maintenance rank lower in Apify Store. If an Actor keeps failing its tests, Apify deprecates it after about a month. From 002a396f3861597f675711dbaeb3a5fb85882b99 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 21 Oct 2026 22:45:57 +0200 Subject: [PATCH 06/10] docs: drop the "Note that" openers on the Actor status page --- sources/platform/actors/publishing/actor-status.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/sources/platform/actors/publishing/actor-status.mdx b/sources/platform/actors/publishing/actor-status.mdx index aead0887d3..fac73aa91f 100644 --- a/sources/platform/actors/publishing/actor-status.mdx +++ b/sources/platform/actors/publishing/actor-status.mdx @@ -41,7 +41,7 @@ To let users know that the Actor might temporarily not work as expected, use the 1. _(Optional)_ In the **Under maintenance message** field, add an additional explanation. 1. Select **Save**. -Note that the **Under maintenance** status makes your Actor rank lower in search results. It's also automatically set when your Actor fails the [automated testing](./testing.mdx) process. +The **Under maintenance** status makes your Actor rank lower in search results. Apify also sets it when your Actor fails the [automated tests](./testing.mdx). ### Mark Actor as deprecated @@ -53,4 +53,4 @@ To let your users know that the Actor is no longer being developed, use the **De Don't delete the Actor as it might break the existing integrations. -Note that the deprecated Actors aren't searchable in Apify Store. The **Deprecated** status is also automatically set when your Actor fails the [automated testing](./testing.mdx) process for 30 days. +Deprecated Actors aren't searchable in Apify Store. Apify also sets the **Deprecated** status when your Actor fails the [automated tests](./testing.mdx) for 30 days. From a8c06b76df39a0d102d5adf293bca9ccd318a328 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 21 Oct 2026 22:48:19 +0200 Subject: [PATCH 07/10] docs: keep the test schedule on the testing page only The status, Store, and Academy pages each restated the deprecation schedule with a different number. Now they link to the one home. --- .../build-and-publish/apify-store-basics/how_store_works.md | 2 +- sources/platform/actors/publishing/actor-status.mdx | 2 +- sources/platform/actors/running/store/index.md | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md index a01922d6c4..81a2652bd6 100644 --- a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md +++ b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md @@ -52,7 +52,7 @@ For details, see [Actor developers](/actors/running/store/actor-developers). It's essential to test your Actors and make sure they work as intended. That's why Apify does it on our side as much as you should do it on yours. -Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check whether an Actor's run with its default input succeeds within 5 minutes. If an Actor fails most of its test runs over three days, Apify labels it under maintenance and notifies the developer. If the Actor keeps failing for another 28 days, Apify deprecates it. +Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check whether an Actor's run with its default input succeeds within 5 minutes. If an Actor keeps failing, Apify labels it under maintenance, notifies the developer, and later deprecates it. For the schedule, see [How we test](/actors/publishing/test#how-we-test). To restore your Actor's health, fix and rebuild it. The tests use the new build within 24 hours. If your Actor can't pass the tests, for example because it needs more than 5 minutes to finish, you can request to skip the tests. For details, see [Actor testing](/actors/publishing/test#what-if-my-actor-cannot-comply-with-the-test-logic). For more control, you can write your own tests with the [Actor Testing](https://apify.com/pocesar/actor-testing) tool from Apify Store. diff --git a/sources/platform/actors/publishing/actor-status.mdx b/sources/platform/actors/publishing/actor-status.mdx index fac73aa91f..d2a5102e51 100644 --- a/sources/platform/actors/publishing/actor-status.mdx +++ b/sources/platform/actors/publishing/actor-status.mdx @@ -53,4 +53,4 @@ To let your users know that the Actor is no longer being developed, use the **De Don't delete the Actor as it might break the existing integrations. -Deprecated Actors aren't searchable in Apify Store. Apify also sets the **Deprecated** status when your Actor fails the [automated tests](./testing.mdx) for 30 days. +Deprecated Actors aren't searchable in Apify Store. Apify also sets the **Deprecated** status when your Actor keeps failing the [automated tests](./testing.mdx). diff --git a/sources/platform/actors/running/store/index.md b/sources/platform/actors/running/store/index.md index b9a6b02f64..f5b3397d36 100644 --- a/sources/platform/actors/running/store/index.md +++ b/sources/platform/actors/running/store/index.md @@ -107,7 +107,7 @@ If an Actor you use is under maintenance: - On the Actor's **Issues** tab, look for an issue that describes your problem. If there isn't one, create one to ask the developer. - To find a replacement, select **Show similar Actors** in the banner, or search [Apify Store](https://apify.com/store). -Actors under maintenance rank lower in Apify Store. If an Actor keeps failing its tests, Apify deprecates it after about a month. +Actors under maintenance rank lower in Apify Store. If an Actor keeps failing the tests, Apify deprecates it. ## Report issues with Actors From e9dec128f89c96c862bacf5b16c4d531a7eb759e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 21 Oct 2026 22:48:19 +0200 Subject: [PATCH 08/10] docs: bold the status labels on the testing page like the other pages do --- sources/platform/actors/publishing/testing.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx index b93349ea01..9c93b66844 100644 --- a/sources/platform/actors/publishing/testing.mdx +++ b/sources/platform/actors/publishing/testing.mdx @@ -9,7 +9,7 @@ sidebar_position: 3 ## Why we test We want to make sure that all Actors in Apify Store are top-notch, or at least as top-notch as they can be. Since there are many of them, we have an automated testing procedure in place that tests all Actors daily. -This helps us to flag Actors that temporarily don't work as expected `under maintenance`, and to automatically `deprecate` Actors that have been broken for more than a month. +This helps us to flag Actors that temporarily don't work as expected as **Under maintenance**, and to automatically mark Actors that have been broken for more than a month as **Deprecated**. If you use an Actor that's under maintenance, see [Actors under maintenance](/actors/running/actors-in-store#actors-under-maintenance). @@ -20,11 +20,11 @@ and expects it to finish with a **Succeeded** status and non-empty default datas ![Actor page](./images/actor-test.webp) -If more than half of the daily test runs in the last three days fail, Apify notifies you and labels the Actor `under maintenance` until you fix it. All test runs in those three days must use the same build, so a new build restarts the count. After another 14 days of failing runs, you get another notification. If the runs still fail 14 days after that, Apify marks the Actor as `deprecated`. +If more than half of the daily test runs in the last three days fail, Apify notifies you and labels the Actor **Under maintenance** until you fix it. All test runs in those three days must use the same build, so a new build restarts the count. After another 14 days of failing runs, you get another notification. If the runs still fail 14 days after that, Apify marks the Actor as **Deprecated**. ## Find out why the test failed -When Apify labels your Actor `under maintenance`, you get a notification in Apify Console and by email. The notification tells you whether the test could start the Actor. The fix differs for each case. +When Apify labels your Actor **Under maintenance**, you get a notification in Apify Console and by email. The notification tells you whether the test could start the Actor. The fix differs for each case. ### The test couldn't start the Actor From c64366e35fbd890ae5fc74af618133c40b2aeae3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Wed, 21 Oct 2026 22:48:19 +0200 Subject: [PATCH 09/10] docs: rename two question-style headings on the testing page The anchor for the skip section changed, so the Academy link follows it. --- .../build-and-publish/apify-store-basics/how_store_works.md | 2 +- sources/platform/actors/publishing/testing.mdx | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md index 81a2652bd6..7b942c443d 100644 --- a/sources/academy/build-and-publish/apify-store-basics/how_store_works.md +++ b/sources/academy/build-and-publish/apify-store-basics/how_store_works.md @@ -54,7 +54,7 @@ It's essential to test your Actors and make sure they work as intended. That's w Apify runs automated tests daily to ensure all Actors on Apify Store are functional and reliable. These tests check whether an Actor's run with its default input succeeds within 5 minutes. If an Actor keeps failing, Apify labels it under maintenance, notifies the developer, and later deprecates it. For the schedule, see [How we test](/actors/publishing/test#how-we-test). -To restore your Actor's health, fix and rebuild it. The tests use the new build within 24 hours. If your Actor can't pass the tests, for example because it needs more than 5 minutes to finish, you can request to skip the tests. For details, see [Actor testing](/actors/publishing/test#what-if-my-actor-cannot-comply-with-the-test-logic). For more control, you can write your own tests with the [Actor Testing](https://apify.com/pocesar/actor-testing) tool from Apify Store. +To restore your Actor's health, fix and rebuild it. The tests use the new build within 24 hours. If your Actor can't pass the tests, for example because it needs more than 5 minutes to finish, you can request to skip the tests. For details, see [Actor testing](/actors/publishing/test#skip-the-automated-tests). For more control, you can write your own tests with the [Actor Testing](https://apify.com/pocesar/actor-testing) tool from Apify Store. ### Actor metrics and reliability score diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx index 9c93b66844..4938ff054a 100644 --- a/sources/platform/actors/publishing/testing.mdx +++ b/sources/platform/actors/publishing/testing.mdx @@ -44,13 +44,13 @@ When a test run fails, the notification links to it. Check its log for the cause If the run timed out, make the test input smaller. Choose `prefill` values that return only a few results, so the run finishes within the 5-minute limit. -## How can I make my Actor healthy again +## Restore a healthy status The best course of action is to fix the Actor and rebuild it. The automatic testing system will pick this up within 24 hours and mark it as healthy. In some cases, your Actor might break because of issues with the target website. In such a case, if your Actor passes the majority of test runs in the next 7 days, it will be marked as healthy automatically. -## What if my Actor cannot comply with the test logic +## Skip the automated tests The automated test skips these Actors: From a929f65c51b67e1a01d6e42df7ff366f0cf41ab0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Micha=C5=82=20Olender?= <92638966+TC-MO@users.noreply.github.com> Date: Thu, 22 Oct 2026 14:44:41 +0200 Subject: [PATCH 10/10] Update sources/platform/actors/publishing/testing.mdx Co-authored-by: Edyta <142720610+szaganek@users.noreply.github.com> --- sources/platform/actors/publishing/testing.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sources/platform/actors/publishing/testing.mdx b/sources/platform/actors/publishing/testing.mdx index 4938ff054a..6df5cb0c9a 100644 --- a/sources/platform/actors/publishing/testing.mdx +++ b/sources/platform/actors/publishing/testing.mdx @@ -9,7 +9,7 @@ sidebar_position: 3 ## Why we test We want to make sure that all Actors in Apify Store are top-notch, or at least as top-notch as they can be. Since there are many of them, we have an automated testing procedure in place that tests all Actors daily. -This helps us to flag Actors that temporarily don't work as expected as **Under maintenance**, and to automatically mark Actors that have been broken for more than a month as **Deprecated**. +Testing helps us flag Actors that temporarily don't work as expected as **Under maintenance**, and to automatically mark Actors that have been broken for more than a month as **Deprecated**. If you use an Actor that's under maintenance, see [Actors under maintenance](/actors/running/actors-in-store#actors-under-maintenance).