> 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/library-preparation/general/library-preparation-general-faq-list/000003454.md).

# BLT PF reagent handling for the Illumina DNA PCR Free workflow questions

**Why is it important for the BLT-PF tube to stay upright in storage?**\
Illumina recommends that the BLT-PF stay upright in storage to enable easy resuspension and avoid bead drying. Make sure beads are thoroughly mixed and resuspended prior to use.

**If there is bead residue that dried inside the BLT-PF tube, is it a problem?**\
No, proceed as normal, but resuspend by inversion and vortexing.

**How to proceed if too much or too little BLT-PF is added to a sample?**\
Using less or more of BLT-PF will impact library yield and size distribution. If various amounts of BLT-PFs were used to create libraries, Illumina recommends individually quantifying the libraries before pooling. Libraries may still be sequenced, though certain sequencing metrics may be affected.

**How to proceed if the samples with BLT-PF are left on the magnet longer than is stated in the protocol?**\
Leaving BLT-PF on the magnet for several extra minutes does not lead to any downstream issues with library prep; however, Illumina does not recommend leaving the library prep for long stretches of time (>10 minutes).

**What happens if BLT-PF beads dry?**\
Overdried BLT-PF beads can reduce library yield.

\*\*What happens if the beads settle out of solution?\*\*Resuspend beads and proceed as normal.

\
\
\ <br>

|                                                                                                                                                                                                                                                                                                                                                                              |
| :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------: |
| *For any feedback or questions regarding this article (Illumina Knowledge Article #3454), contact Illumina Technical Support* [*techsupport@illumina.com*](mailto:techsupport@illumina.com?subject=Question%2FFeedback%20Regarding%20Illumina%20Knowledge%20Article%20#000003454%20-%20Library%20Preparation%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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://knowledge.illumina.com/library-preparation/general/library-preparation-general-faq-list/000003454.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.