We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There is the strange behavior about workflow fire. I confirmed the behavior by the following step.
$ cat sample.dig schedule: minutes_interval>: 5 skip_on_overtime: true +task1: echo>: ${session_time} $ digdag push sample 2021-11-10 14:06:52 +0900: Digdag v0.10.3 Creating .digdag/tmp/archive-1710945669874406031.tar.gz... Archiving sample.dig Workflows: sample.dig Uploaded: id: 1 name: sample revision: 11b54a11-63f8-4072-9905-66ffa8fa4464 archive type: db project created at: 2021-11-10T05:07:08Z revision updated at: 2021-11-10T05:07:08Z Use `digdag workflows` to show all workflows.
> digdag disable sample 2021-11-10 14:10:32 +0900: Digdag v0.10.3 Disabled schedule id: 1
> digdag reschedule --skip-to '2021-11-10 14:25:00 +0900' 2021-11-10 14:16:01 +0900: Digdag v0.10.3 id: 1 workflow: sample disabled at: 2021-11-10 14:10:43 +0900 (5m 29s ago) next session time: 2021-11-10 05:25:00 +0000 next scheduled to run at: 2021-11-10 14:25:00 +0900 (in 8m 47s) Use `digdag schedules` to show schedules. > digdag enable sample 2021-11-10 14:16:22 +0900: Digdag v0.10.3 Enabled schedule id: 1 > digdag push sample 2021-11-10 14:17:06 +0900: Digdag v0.10.3 Creating .digdag/tmp/archive-4366420844614961888.tar.gz... Archiving sample.dig Workflows: sample.dig Uploaded: id: 1 name: sample revision: 2310e8ed-c9cf-477e-a9b3-43963dc27273 archive type: db project created at: 2021-11-10T05:07:08Z revision updated at:2021-11-10T05:17:06Z Use `digdag workflows` to show all workflows.
> digdag sessions asmple 2021-11-10 14:22:40 +0900: Digdag v0.10.3 Sessions: session id: 1 attempt id: 1 uuid: 75f32229-607b-4ce4-ade4-be9a2caf6a18 project: sample workflow: sample session time: 2021-11-10 05:10:00 +0000 retry attempt name: params: {"last_session_time":"2021-11-10T05:05:00+00:00","next_session_time":"2021-11-10T05:15:00+00:00"} created at: 2021-11-10 14:10:00 +0900 kill requested: false status: success session id: 2 attempt id: 2 uuid: 95938f6c-16e7-4d06-a399-767104a5540a project: sample workflow: sample session time: 2021-11-10 05:15:00 +0000 retry attempt name: params: {"last_session_time":"2021-11-10T05:10:00+00:00","next_session_time":"2021-11-10T05:20:00+00:00","last_executed_session_time":"2021-11-10T05:10:00+00:00"} created at: 2021-11-10 14:17:06 +0900 kill requested: false status: success
I don't know why this workflow run at 2021-11-10 14:17:06 +0900 (as session time: 2021-11-10 05:15:00 +0000)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
There is the strange behavior about workflow fire.
I confirmed the behavior by the following step.
I don't know why this workflow run at 2021-11-10 14:17:06 +0900 (as session time: 2021-11-10 05:15:00 +0000)
The text was updated successfully, but these errors were encountered: