Hilary James Oliver

Agreed on documenting use of a stop point rather than final cycle point, to allow extending a workflow run more easily. But, a stop point requires trickier graph config if...

> We'd rather not, the FCP approach is conceptually awkward and are keen to move users away from it. That's all very well, but it's going to happen anyway, as...

> > We'd rather not, the FCP approach is conceptually awkward and are keen to move users away from it. > > That's all very well, but it's going to...

I don't think we're disagreeing on the fundamental point here. I'm just saying in addition to that, we still need to document how to restart after extending the FCP *if...

@ColemanTom - we discussed this in the project meeting today. We wondered whether having the disk yanked out from underneath you is really something that Cylc should be expected to...

Note that `cylc play` and `cylc reinstall` fail if the existing run-dir symlinks are dangling, which is reasonable: ``` WorkflowFilesError: /home/oliverh/cylc-run/bug/runN symlink not valid ``` I wonder if it might...

> we need them to succeed with no more actions required than to re-run the job. First level support will not have access to create any missing directories or symbolic...

@ColemanTom - I'm not dismissing the idea outright, at least not yet, it seems worth considering, especially if it's true that no other external manual intervention would be required for...

> I just assumed there was fear of a race condition - and perhaps in a non-POSIX linux environment there is? Ah, yeah .. maybe that's it (I'd have thought...

> Changes like this are high risk and require a lot of thinking and testing (this may have been protecting us for some use cases). It was added (without an...