Skip to content

Commit d1c9700

Browse files
jirimoravcikTC-MO
andauthored
Apply suggestions from code review
Co-authored-by: Michał Olender <[email protected]>
1 parent cbb8346 commit d1c9700

File tree

1 file changed

+9
-2
lines changed

1 file changed

+9
-2
lines changed

sources/platform/actors/development/programming_interface/actor_standby.md

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -74,8 +74,15 @@ inputs and outputs in your README.
7474

7575
### Readiness probe
7676

77-
Before Actor standby runs are ready to serve requests, Apify platform checks if the web server is ready via a readiness probe.
78-
The platform sends a GET request to the path `/` with a header `x-apify-container-server-readiness-probe`. If the header is present in the request, you can perform an early return with a simple response to prevent wasting resources. Note that you have to return a response, otherwise the Actor run will never be ready and therefore won't be able to process any requests.
77+
Before Actor standby runs are ready to serve requests, the Apify platform checks the web server's readiness using a readiness probe.
78+
The platform sends a GET request to the path `/` with a header `x-apify-container-server-readiness-probe`. If the header is present in the request, you can perform an early return with a simple response to prevent wasting resources.
79+
80+
:::note Return a response
81+
82+
You must return a response; otherwise, the Actor run will never be marked as ready and won't process requests.
83+
84+
:::
85+
7986

8087
See example code below that distinguishes between "normal" and "readiness probe" requests.
8188

0 commit comments

Comments
 (0)