You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Leaving this here for tracking. There are 2x related issues with Job statuses:
Status after update: After an update, the last run of a job isn't retained.
When there is an update available and automatic updates are enabled, cosmos updates / restarts itself automatically despite a running job. After restart, the job status is "stopped" and logs cleared. In fact, the Job is still running though and new log entries are still tracked/shown in cosmos.
I have a job which calls a script called mover.sh configured. The job is still running and it still puts out logs.
What should have happened?
Logs and Last run status should be retained in case of cosmos-update.
automatic cosmos update should check for running jobs and delay its update.
System details
OS: Debian Bookworm
Browser: Firefox
Version: 0.17.0 docker-free
The text was updated successfully, but these errors were encountered:
What happened?
Leaving this here for tracking. There are 2x related issues with Job statuses:
I have a job which calls a script called mover.sh configured. The job is still running and it still puts out logs.
What should have happened?
System details
The text was updated successfully, but these errors were encountered: