# 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:** 6

<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 2, 2023, 3:25am UTC](https://cylc.discourse.group/t/continuing-a-run-that-completed/640/6 "2023-05-02T03:25:41Z")

</div>

> [@hilary.j.oliver](#):
>
> But you also need to be aware of the flow that the spawned tasks belong to.

And at the moment that involves looking at the scheduler log.

If you don’t deliberately trigger new flows (as opposed to triggering tasks as part of the original flow, which is the default) you shouldn’t have to worry about this. But we have seen some users get into trouble because they weren’t sure if they needed to trigger new flows or not.

Flows and triggering are pretty well [documented here](https://cylc.github.io/cylc-doc/stable/html/user-guide/running-workflows/reflow.html) although there’s bound to be some details and edge cases that we need to clarify yet.

---

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