# Continuing a run that completed

**URL:** <https://cylc.discourse.group/t/continuing-a-run-that-completed/640>\
**Category:** Cylc 8 Migration\
**Created:** [April 28, 2023, 9:26am UTC](https://cylc.discourse.group/t/continuing-a-run-that-completed/640 "2023-04-28T09:26:32Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![hilary.j.oliver](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/hilary.j.oliver/32/4_2.png) [@hilary.j.oliver](https://cylc.discourse.group/u/hilary.j.oliver)\
**Post date:** [May 1, 2023, 1:57am UTC](https://cylc.discourse.group/t/continuing-a-run-that-completed/640/4 "2023-05-01T01:57:01Z")

</div>

> [@srennie](#):
>
> And then I think, why don’t I just set-outputs on the entire previous cycle?

Unfortunately `cylc set-outputs` is the prime offender in the short list of triggering and flow-related commands that aren’t fully user-friendly yet.

For the moment, if you need to use that command, what it does is tell the scheduler to carry on _as if_ the outputs of the target task had been completed. So downstream tasks that depend on those outputs will be spawned, and will be ready to run immediately - unless they have other prerequisites that need to be “set” as well. But you also need to be aware of the flow that the spawned tasks belong to. With `cylc trigger` the default is to belong to the current flow (and as Oliver pointed out, on restarting a finished workflow there is no current flow). With `cylc set-outputs` the default is still no-flow, I think, so you’ll need to use (e.g.) the `--flow=1` command line argument if you want the newly-triggered tasks to flow on in the graph, even when there is a current active flow.

---

_[View the full topic](https://cylc.discourse.group/t/continuing-a-run-that-completed/640)._