# Specifying equivalent of -dump-hashes on Seqera Platform

**URL:** https://community.seqera.io/t/specifying-equivalent-of-dump-hashes-on-seqera-platform/917
**Category:** Ask for help
**Tags:** platform
**Created:** [July 3, 2024, 5:08pm UTC](https://community.seqera.io/t/specifying-equivalent-of-dump-hashes-on-seqera-platform/917 "2024-07-03T17:08:22Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![didillysquat](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/didillysquat/32/819_2.png) [@didillysquat](https://community.seqera.io/u/didillysquat)
#### Post date: [July 3, 2024, 5:08pm UTC](https://community.seqera.io/t/specifying-equivalent-of-dump-hashes-on-seqera-platform/917/1 "2024-07-03T17:08:22Z")

</div>

When resuming our pipelines that have been launched from Seqera Tower, either via the LaunchPad, or programmatically via an Action, the resume function works inconsistently. When using `-resume` on the same pipelines launched locally, resume works every time. To debug this, I’d like to examine the cache hashes.

When running a Nextflow pipeline from the CLI I can add `-dump-hashes`.

Where and how can I add this argument in the Seqera Tower interface to the same effect?

---

<div class="post-metadata">

### Author: ![didillysquat](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/didillysquat/32/819_2.png) [@didillysquat](https://community.seqera.io/u/didillysquat)
#### Post date: [July 3, 2024, 5:39pm UTC](https://community.seqera.io/t/specifying-equivalent-of-dump-hashes-on-seqera-platform/917/2 "2024-07-03T17:39:36Z")

</div>

Found it in the docs here: [https://docs.seqera.io/platform/23.2.0/faqs#nextflow-configuration](https://docs.seqera.io/platform/23.2.0/faqs#nextflow-configuration)

" As of Nextflow v22.09.1-edge, when invoking a pipeline from Tower, you can specify [Nextflow CLI run arguments](https://www.nextflow.io/docs/latest/cli.html?highlight=dump#run) by setting the `NXF_CLI_OPTS` environment variable via pre-run script:

`export NXF_CLI_OPTS='-dump-hashes'`

---

<div class="post-metadata">

### Author: ![didillysquat](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/didillysquat/32/819_2.png) [@didillysquat](https://community.seqera.io/u/didillysquat)
#### Post date: [July 3, 2024, 9:01pm UTC](https://community.seqera.io/t/specifying-equivalent-of-dump-hashes-on-seqera-platform/917/3 "2024-07-03T21:01:11Z")

</div>

> [@didillysquat](#):
>
> [https://docs.seqera.io/platform/23.2.0/faqs#nextflow-configuration](https://docs.seqera.io/platform/23.2.0/faqs#nextflow-configuration)

Sadly, on implementation, this didn’t work ☹

Relaunching with:

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/1X/40351564aba5589ba702d6e523a3a073308a5c65.png)

Led to…

 ![image](https://europe1.discourse-cdn.com/flex013/uploads/seqera/original/1X/ba9405a724632ce32a38e81fb19402bf7ceb7f34.png)

This was with `N E X T F L O W ~ version 24.04.2`

---

<div class="post-metadata">

### Author: ![Adam\_Talbot](https://dub1.discourse-cdn.com/flex013/user_avatar/community.seqera.io/adam_talbot/32/62_2.png) [@Adam\_Talbot](https://community.seqera.io/u/Adam_Talbot)
#### Post date: [July 4, 2024, 3:06pm UTC](https://community.seqera.io/t/specifying-equivalent-of-dump-hashes-on-seqera-platform/917/4 "2024-07-04T15:06:52Z")

</div>

You can enable this in the Nextflow configuration section using:

```auto
dumpHashes = true

```

It’s a little hard to find because it’s under [Configuration — Nextflow documentation](https://www.nextflow.io/docs/latest/config.html#miscellaneous)