# An error occurred (ResourceInUseException) when calling the DescribeTable operation: Table is in ARCHIVING state and cannot be described

- **ID:** `aws/dynamodb-table-in-archiving-state`
- **Domain:** aws
- **Category:** resource_error
- **Error Code:** `ResourceInUseException`
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

The DynamoDB table is being archived (e.g., via a backup or deletion process), and operations like DescribeTable are blocked until archiving completes.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| dynamodb-2012-08-10 | active | — | — |
| aws-cli/2.17.0 | active | — | — |

## Workarounds

1. **Wait for the archiving process to complete. Monitor table status with `aws dynamodb wait table-exists --table-name mytable` or check CloudWatch events for backup completion.** (95% success)
   ```
   Wait for the archiving process to complete. Monitor table status with `aws dynamodb wait table-exists --table-name mytable` or check CloudWatch events for backup completion.
   ```
2. **If archiving is taking too long, contact AWS Support to expedite or cancel the operation, as it may be stuck due to large table size or throttling.** (60% success)
   ```
   If archiving is taking too long, contact AWS Support to expedite or cancel the operation, as it may be stuck due to large table size or throttling.
   ```
3. **Use DynamoDB Streams to capture changes before archiving begins; after archiving completes, recreate the table and replay changes.** (70% success)
   ```
   Use DynamoDB Streams to capture changes before archiving begins; after archiving completes, recreate the table and replay changes.
   ```

## Dead Ends

- **Force delete the table using `aws dynamodb delete-table`** — If the table is in ARCHIVING state, it is already being deleted or backed up; delete-table will fail with the same error. (85% fail)
- **Restore the table from a backup while it is archiving** — Restore operations require the table to be in ACTIVE state; archiving blocks both reads and writes. (90% fail)