# Failed (remote) cylc task fails but server fails to notice

**URL:** <https://cylc.discourse.group/t/failed-remote-cylc-task-fails-but-server-fails-to-notice/507>\
**Category:** Cylc Support\
**Created:** [July 22, 2022, 12:32am UTC](https://cylc.discourse.group/t/failed-remote-cylc-task-fails-but-server-fails-to-notice/507 "2022-07-22T00:32:20Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![Clint\_Seinen](https://yyz2.discourse-cdn.com/free1/user_avatar/cylc.discourse.group/clint_seinen/32/185_2.png) [@Clint\_Seinen](https://cylc.discourse.group/u/Clint_Seinen)\
**Post date:** [July 22, 2022, 6:36pm UTC](https://cylc.discourse.group/t/failed-remote-cylc-task-fails-but-server-fails-to-notice/507/3 "2022-07-22T18:36:45Z")

</div>

Thank you very much for the comprehensive answer @oliver.sanders ! I think this should give me some things to track down to try to figure out the issue. I think @swartn was seeing similar issues on our old system, so its probably related.

RE: the `install target`, yeah we are still using the hack that is discussed [here](https://cylc.discourse.group/t/setting-up-a-platform-config-for-machines-that-share-a-home-directory/446) because all our machines share a home but not where the scratch spaces are, so we make links under `cylc-run`

---

_[View the full topic](https://cylc.discourse.group/t/failed-remote-cylc-task-fails-but-server-fails-to-notice/507)._