-
Notifications
You must be signed in to change notification settings - Fork 34
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.
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
Crontab sets directly to error when runParameters is not found #224
Labels
enhancement
New feature or request
Comments
luissian
added a commit
to luissian/iskylims
that referenced
this issue
Aug 29, 2023
…runParameters is not found
Merged
implemented this issue in PR 226 |
luissian
added a commit
to luissian/iskylims
that referenced
this issue
Aug 31, 2023
luissian
added a commit
to luissian/iskylims
that referenced
this issue
Aug 31, 2023
luissian
added a commit
to luissian/iskylims
that referenced
this issue
Sep 3, 2023
saramonzon
pushed a commit
that referenced
this issue
Sep 4, 2023
saramonzon
pushed a commit
that referenced
this issue
Sep 4, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of feature
This behaviour makes that runs are set to error when some transfer issues happen, the folder may exists but runParameter file is yet to be copied.
We need to add a time counter so it waits 2-3 cron cycles before it sets the run to error so it can wait for the runParameters file to be copied if that's the case.
The text was updated successfully, but these errors were encountered: