# Errors in global init-script causing tasks to disappear in Cylc 8

**URL:** <https://cylc.discourse.group/t/errors-in-global-init-script-causing-tasks-to-disappear-in-cylc-8/800>\
**Category:** Cylc Support\
**Created:** [November 7, 2023, 4:43pm UTC](https://cylc.discourse.group/t/errors-in-global-init-script-causing-tasks-to-disappear-in-cylc-8/800 "2023-11-07T16:43:28Z")\
**Posts on this page:** 1\
**Showing post:** 14

<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:** [November 10, 2023, 10:00pm UTC](https://cylc.discourse.group/t/errors-in-global-init-script-causing-tasks-to-disappear-in-cylc-8/800/14 "2023-11-10T22:00:17Z")

</div>

> [@hilary.j.oliver](#):
>
> But unfortunately it does not explain why `test_C` would be removed on submit-failure. That’s still a mystery!

A-ha!!! @russbnavy - you’re not running in Cylc 7 back-compat mode are you? (i.e., with a `suite.rc` config file, not `flow.cylc`). The [8.2.3 release announcement](https://cylc.discourse.group/t/cylc-8-2-0-released/702/8) reminded me that back-compat mode had a more severe version of the submit-failed handling bug.

Running my test case in back-compat mode does indeed result in this:

```auto
CRITICAL - [1/D submitted job:01 flows:none] submission failed
INFO - [1/D submitted job:01 flows:none] => submit-failed
DEBUG - [1/D submit-failed job:01 flows:none] task proxy removed (finished) # !!!

```

Hopefully that explains it. If so, there’s nothing wrong with your system. You just need to upgrade to 8.2.3, or upgrade your workflow config to Cylc 8.

---

_[View the full topic](https://cylc.discourse.group/t/errors-in-global-init-script-causing-tasks-to-disappear-in-cylc-8/800)._