David Matthews

> Proposal: if there are no existing flows, triggered tasks should default to all previous flows. I don't think this is safe. When triggering historical tasks I think it would...

I'd interpreted "all previous flow numbers" to mean all flow numbers from the entire workflow. Does it actually mean all previous flow numbers from the triggered task? If so then...

> Yes, but if you manually triggered the next task before shutdown - while that final off-piste task was still running - instead of after restart, it would get that...

> I think restart should always use the previous config. It should also not repeat any remote file installation.

> Duplicate of #4516 No - that was a different bug

> Note, this impacts Rose worse than Cylc, however, with Rose we actually need the PYTHONPATH to be preserved because it will be required for the Rose "command". Perhaps we...

I would prefer the readlink approach suggested in the original issue. Something like: ```sh if [[ ! -e "${CYLC_WORKFLOW_SHARE_DIR}" ]]; then if [[ -L "${CYLC_WORKFLOW_SHARE_DIR}" ]]; then mkdir -p $(readlink...

@trwhitcomb - note that you can split the PBS `-l` options into separate directives, see http://cylc.github.io/cylc/html/multi/cug-htmlse11.html#11.2.5

This option is only available on recent versions of `timeout` (e.g. it works on RHEL7 but not RHEL6) so I think it would have to be configurable

We already have the case that trigger actually just queues a task and you need a second trigger to make it run immediately. We could extent this to: * Triggering...