> For the complete documentation index, see [llms.txt](https://documentation.2pintsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.2pintsoftware.com/osd-toolkit/introduction/the-2pint-alternate-content-provider/tracking-progress-and-results.md).

# Tracking progress and results

The following keys are written to the registry under HKLM\Software\2pint Software\BITSTS\\\<DeploymentID>\\\<ContentID> registry path.

<table><thead><tr><th width="312">Registry value</th><th>Description</th></tr></thead><tbody><tr><td>BytesFromPeers</td><td>Bytes from cache/peers for current job</td></tr><tr><td>BytesFromSource</td><td>Bytes from the server for the current job</td></tr><tr><td>BytesTotal</td><td>Total bytes of the download</td></tr><tr><td>Context</td><td>Error context</td></tr><tr><td>Description</td><td>Error description</td></tr><tr><td>EndTime</td><td>Date time when the job ended</td></tr><tr><td>Error</td><td>Last error during this download</td></tr><tr><td>ExitCode</td><td>The return code of the ACP, non zero means download failed</td></tr><tr><td>FilesTotal</td><td>Number of files in download</td></tr><tr><td>FilesTransferred</td><td>How many files have been transferred</td></tr><tr><td>JobId</td><td>The GUID of the BITS job</td></tr><tr><td>SequenceBytesFromPeersAfter</td><td>How many bytes the sequence had pulled from peers at the end of this step</td></tr><tr><td>SequenceBytesFromPeersBefore</td><td>How many bytes the sequence had pulled from peers at the beginning of this step</td></tr><tr><td>SequenceBytesFromSourceAfter</td><td>How many bytes the sequence had pulled from source at the end of this step</td></tr><tr><td>SequenceBytesFromSourceBefore</td><td>How many bytes the sequence had pulled from source at the beginning end of this step</td></tr><tr><td>SmallFilesCount</td><td>Number of small files in content that cannot be BranchCached</td></tr><tr><td>SmallFilesSize</td><td>Total size of the small files put together, this is the total size that cannot be peered and has to be downloaded from server</td></tr><tr><td>Source</td><td>The URL that is the source of this download</td></tr><tr><td>StartTime</td><td>The date time when this download started</td></tr><tr><td>Step</td><td>The step number of which this download is part of, note that multiple downloads can be done for the same step</td></tr><tr><td>StepName</td><td>The step name for this download, note that multiple downloads can be done for the same step</td></tr></tbody></table>


---

# 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://documentation.2pintsoftware.com/osd-toolkit/introduction/the-2pint-alternate-content-provider/tracking-progress-and-results.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.