> For the complete documentation index, see [llms.txt](https://knowledge.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000002449.md).

# Troubleshooting a Software Shutdown Issue Warning on the NextSeq 500/550 with NCS 4.0.X

The following message may appear when shutting down or restarting the NextSeq 500/550 and can be associated with Proactive being enabled. This warning **does not affect** run quality or system performance.

"Software shutdown issue(s):\
Data from the previous sequencing run is being sent to persistent storage. Select Cancel to wait for the transfer to finish.\
Do you want to proceed?"

![](https://761066130-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FGM9W2DuBTgEXv1ClCm8H%2Fuploads%2Fgit-blob-f99c443c796f4033d620fb76fee130e76789f73d%2Fimage1.png?alt=media\&token=1786f6e9-3352-462b-ae0a-e732bbfdf121)

**Troubleshooting steps:**

1. If the instrument **not connected to the internet**, disable Proactive monitoring as follows:
   1. Navigate to the NextSeq Control Software.
   2. Select **System Settings**.
   3. Deselect the option **Send Instrument Performance Data to Illumina**.
2. If all runs have completed transfer and/or upload, apply instructions found in the following article: [Troubleshooting Universal Copy Server error on the NextSeq 500/550 (NCS 4.0+)](https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000002770.md).
3. If the most recent run is still being transferred and/or uploaded, it is acceptable to select **Proceed** and ignore the message.
   * If run data had not finished copying, Universal Copy Service (UCS) will continue process after instrument has been restarted.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                        |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #2449), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000002449%20-%20Instrumentation%20\&body=Dear%20Illumina%20Technical%20Support,%0D%0A%0D%0A)*.* |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledge.illumina.com/instrumentation/nextseq-500-550/instrumentation-nextseq-500-550-troubleshooting-list/000002449.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
