> For the complete documentation index, see [llms.txt](https://help.bioinsight.illumina.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.bioinsight.illumina.com/basespace/releases/previous-releases/2017/4.15.0.md).

# 4.15.0

### January 17, 2017 - 4.15 - Usage Tracking Improvements

* Features:
  * Improvements to bill details page
  * Update to App Results page to show compute charges to two decimal places
  * Improved Launch App dropdown menu response time
  * Warn users if there are operations in progress when they empty the trash
  * Added email notification for apps that aborted due to error
* Bug fixes:
  * Fixed issue that prevented removing of collaborators from the Share dialog
  * Fixed issue within the Developer Portal that truncated the Preview section
  * Fixed issue that limited the number of Workgroups listed within the Workgroup menu
  * Fixed issue that allowed users to move data in a pending transfer state to trash. User now needs to cancel transfer prior to move.


---

# 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://help.bioinsight.illumina.com/basespace/releases/previous-releases/2017/4.15.0.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.