Hilary James Oliver
Hilary James Oliver
> Validate, reinstall and apply changes to a workflow. > > Validate and reinstall a workflow then either: > > * "Reload" the workflow (if it is running), > *...
We recently kind-of agreed that: > Remove-like functionality is the right way to chop off a bit of graph However the [cylc remove extension proposal](https://cylc.github.io/cylc-admin/proposal-remove.html) does not achieve that except...
Reportedly, `cylc vr` on a running workflow (i.e., reload) does not update the clock trigger time. Stopping the scheduler first (i.e., restart) does get it right. [UPDATE] Confirmed, using a...
Close #6259 Close #6260 User-defined xtriggers (including wall-clock) need to be reconstructed after reload (to pick up changes), but auto-defined ones (retries) must be retained. **Check List** - [x] I...
```ini [scheduling] initial cycle point = now [[graph]] PT1M = "foo" [runtime] [[foo]] script = sleep 10 ``` Run the above, change the source to this then `cylc vr` (reload):...
We need to: - [ ] allow xtriggers to be reset (forced to be satisfied or unsatisfied) - [ ] document the current workaround in the meantime REF: https://cylc.discourse.group/t/can-i-reset-an-xtrigger/87/2?u=hilary.j.oliver
See discussion at #6221 - we need a way for users to easily see what happens downstream of arbitrary points in the graph, particularly prior to staging a runtime intervention....
Workflows with non-clock xtriggers typically can't be run easily in simulation modes. We should probably add a `[simulation]` config item to either disable xtriggers (default True) or perhaps replace them...
Currently, we demote task messages to DEBUG level if they are more or less redundant with logged state changes. However, this isn't ideal for job failure messages because, - if...
```cylc [scheduling] [[graph]] R1 = "foo => a & b & c" [runtime] [[foo]] script = "sleep 360" [[a, b, c]] script = false execution retry delays = PT5S ```...