# Statuses ## Request statuses | Status | Meaning | | ------------ | -------------------------------------------------------------------- | | in\_queue | Workload is in the queue and is yet to be consumed by the API | | in\_progress | Workload has been pulled by the API and is currently being processed | | completed | Workload has completed with success | | failed | Workload encountered an error during processing | ## Replica states The replica states of an API can be inspected by running `cortex describe `. Here are the possible states for each replica in an API: | State | Meaning | | -------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Ready | Replica is running and it has passed the readiness checks | | ReadyOutOfDate | Replica is running and it has passed the readiness checks (for an out-of-date replica) | | NotReady | Replica is running but it's not passing the readiness checks; make sure the server is listening on the designed port of the API | | Pending | Replica is in a pending state (waiting to get scheduled onto a node) | | Creating | Replica is in the process of having its containers created | | ErrImagePull | Replica was not created because one of the specified Docker images was inaccessible at runtime; check that your API's docker images exist and are accessible via your cluster's AWS credentials | | Failed | Replica couldn't start due to an error; run `cortex logs ` to view the logs | | Killed | Replica has had one of its containers killed | | KilledOOM | Replica was terminated due to excessive memory usage; try allocating more memory to the API and re-deploy | | Stalled | Replica has been in a pending state for more than 15 minutes; see [troubleshooting](/0.40/workloads/realtime/troubleshooting.md) | | Terminating | Replica is currently in the process of being terminated | | Unknown | Replica is in an unknown state | --- # 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://docs.cortexlabs.com/0.40/workloads/async/statuses.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.