# Artifact data and refresh schedules

Inspect data dependencies, retention, freshness, and the schedules attached to an artifact.

## Where to find it

Open **Apps & Workspaces**, choose the workspace, and open the artifact. Its header and drawers contain the settings for this guide.

Address: `/artifacts/:id`. Open the saved resource from the product rather than typing this address.

## Inspect data

Open **Item details > Data** to review registered tables and their retention. Check the owning source and current freshness before interpreting an app's output. Previewed rows and cached datasets are not proof of a complete or current source sync.

## Review attached schedules

Open **Item details > Schedules** and inspect the relevant schedule. Review its target, enabled state, timing, attached context, and most recent run. Use the [schedule detail guide](/docs/schedule-details) for configuration, history, and recovery.

## Recover stale output

1. Identify the table, source, or dataset used by the artifact.
2. Inspect its latest source sync or refresh run.
3. Correct the reported blocker before retrying.
4. Check that the successful run updated the expected data and app output.

Artifact-owned table retention matters during deletion: tables labeled **artifact_lifetime** are removed with their rows. **operator_managed** tables are retained. Attached schedules are also torn down by artifact deletion, which fails if cleanup cannot be completed safely.

## Related guides

- [Source details](/docs/source-details)
- [Table details](/docs/table-details)
- [Scheduled Work](/docs/scheduled-work)
- [Artifact settings and deletion](/docs/artifact-settings)