`ArchiveActivity` is the platform entity that records **job metadata for Salesforce Archive jobs** (archive, purge, analyze, unarchive, export). Every archive job produces one `ArchiveActivity` record; you read it to learn a job's status, progress, and outcome, and you use its `Id` + `Type` to download the job's logs.
| Name field | Auto-number, mask `ARCV-{0000000000}` |
| Flow-enabled? | **No** — `isProcessEnabled=false`. A Flow "Get Records" element on it fails: "You can't get ArchiveActivity records in a flow." Query via SOQL / Connect / Reports. |
| `FailureReason` | Long text | Why the job failed/partially completed (system error messages or policy-level failures) |
| `RecordsSizeInMb` | Text | Estimated total size of processed records (MB) |
> The entity also defines a `ProgressIcon` display formula for list views; it is not useful for programmatic monitoring — read `Status`, `ProgressPercentage`, and the count fields directly.
## How ArchiveActivity links to the Connect API
The log-download endpoints (`get-execution-details-stream-url`, `get-failed-records-stream-url`) take:
-`requestId` = an `ArchiveActivity`**`Id`** (`8qv…`) of a completed, log-producing job, and
-`reportType` = that same activity's **`Type`** value.
So the monitoring pattern is: **query `ArchiveActivity` → pick the job(s) of interest → pass each job's `Id` and `Type` to the stream-url operation → check `url != null`.** See `../examples/monitor-failed-jobs.md`.
## Example SOQL
```sql
-- Failed or in-progress jobs in the last 7 days, newest first