Skip to content

docs: fix waitForFinish description #1578

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 13, 2025
Merged

docs: fix waitForFinish description #1578

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
ffd45cb
docs: fix waitForFinish description
TC-MO May 13, 2025
7747e77
further fixes of waitForFinish
TC-MO May 13, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion apify-api/openapi/paths/actor-runs/actor-runs@{runId}.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,7 +88,7 @@ get:
The maximum number of seconds the server waits for the run to finish. By
default it is `0`, the maximum value is `60`. <!--
MAX_ACTOR_JOB_ASYNC_WAIT_SECS -->
If the build finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
If the run finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
otherwise it will have a transitional status (e.g. `RUNNING`).
style: form
explode: true
Expand Down
2 changes: 1 addition & 1 deletion apify-api/openapi/paths/actor-tasks/actor-tasks@{actorTaskId}@runs.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -231,7 +231,7 @@ post:
description: |
The maximum number of seconds the server waits for the run to finish. By
default, it is `0`, the maximum value is `60`. <!-- MAX_ACTOR_JOB_ASYNC_WAIT_SECS -->
If the build finishes in time then the returned run object will have a
If the run finishes in time then the returned run object will have a
terminal status (e.g. `SUCCEEDED`),
otherwise it will have a transitional status (e.g. `RUNNING`).
style: form
Expand Down
2 changes: 1 addition & 1 deletion apify-api/openapi/paths/actors/acts@{actorId}@runs.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -224,7 +224,7 @@ post:
description: |
The maximum number of seconds the server waits for the run to finish. By
default, it is `0`, the maximum value is `60`. <!-- MAX_ACTOR_JOB_ASYNC_WAIT_SECS -->
If the build finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
If the run finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
otherwise it will have a transitional status (e.g. `RUNNING`).
style: form
explode: true
Expand Down
2 changes: 1 addition & 1 deletion apify-api/openapi/paths/actors/acts@{actorId}@runs@{runId}.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ get:
description: |
The maximum number of seconds the server waits for the run to finish. By
default it is `0`, the maximum value is `60`. <!-- MAX_ACTOR_JOB_ASYNC_WAIT_SECS -->
If the build finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
If the run finishes in time then the returned run object will have a terminal status (e.g. `SUCCEEDED`),
otherwise it will have a transitional status (e.g. `RUNNING`).
style: form
explode: true
Expand Down