# Cycle Status Data Stream uses a precedence algorithm to control and enforce proper data streams throughout. {% hint style="warning" %} In order for a cycle status to be updated, the new cycle status must have a higher precedence than the previous status. {% endhint %} | Code | Name | Description | Precedence | | ---- | ---------- | --------------------------------------------------------------------------------------------------------------- | :--------: | | E | Empty | Empty is reserved for system use and occurs when a data stream is missing both a serial number and part number. | 0 | | T | In-Transit | In-Transit is reserved for system use and occurs when a data stream has both a serial number and part number. | 1 | | I | In-Process | In-Process is reserved for system use and occurs when a data stream is missing both accept and reject signals. | 2 | | A | Accept | Accept occurs when a data stream has an accept and not a reject signal. | 3 | | X | Reject | Reject occurs when a data stream has a reject signal. | 4 | | R | Repair | Repair is reserved for Teardown use and occurs when an operator completes the repair process. | 5 | | S | Scrap | Scrap is reserved for Teardown use and occurs when an operation completes the scrap process. | 6 | --- # Agent Instructions: 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: ``` GET https://support.getdatastream.com/support/definitions/cycle-status.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.