Skip to content

update timeout period for workflow #303

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 1 commit into from
Aug 12, 2021
Merged

update timeout period for workflow #303

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
8 changes: 4 additions & 4 deletions _docs/troubleshooting/common-issues/workflow-terminated-by-system.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,10 @@ toc: true
If you have a long workflow that takes more than several minutes to finish, you might discover that it is automatically
terminated by the system.

By default, the system will terminate a build step that seems "inactive" after 15 minutes. If your
step does not print anything in the log for 15 minutes, it will be considered inactive.
By default, the system will terminate a build step that seems "inactive" after 45 minutes. If your
step does not print anything in the log for 45 minutes, it will be considered inactive.

Therefore, the build will be terminated if in more than 15 minutes there isn't any update in the build process logs.
Therefore, the build will be terminated if in more than 45 minutes there isn't any update in the build process logs.

## Solution

Expand All @@ -30,7 +30,7 @@ You can choose one of the following suggestions to resolve it:
If your workflow process has been terminated by the system for another reason that is not listed here, please let us know.
{{site.data.callout.end}}

As an example, if you have a long running process that takes more than 15 minutes you can try adding
As an example, if you have a long running process that takes more than 45 minutes you can try adding
a command that echoes something every 10 minutes to STDOUT before your command, like this:


Expand Down