# Schedule details and run history

Review a schedule target, timing, context, run activity, and results.

## Where to find it

Open **Scheduled Work**, find the schedule, and open its details. An artifact can also link to its attached schedules.

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

## Open the schedule inspector

Open a schedule from **Scheduled Work** or an artifact's Schedules section. Its inspector shows the target, Activity, Results, and editable settings while retaining the list context.

## Edit and save

Review **Name**, cadence/timezone, **Enabled**, **Notify me if it fails**, and the appropriate **Instructions** or saved-task configuration. Saved tasks can expose **Saved task endpoint** and **Advanced task options JSON**. Use only the intended supported task and valid JSON.

Choose **Save changes** and wait for **Changes saved**. Changing a field is not a save. Turning **Enabled** off pauses future runs after saving; turning it on resumes them. It does not cancel work already executing. Leaving with unsaved edits asks whether to discard them; leaving during a save or deletion does not cancel that operation.

## App-managed schedules

The inspector labels these **App-managed schedule**. You can change cadence/timezone or pause/resume, but the app controls Name, Instructions, saved-task settings, and failure notification. The inspector does not offer Delete for them. Change the app-managed definition through its owning app workflow rather than looking for an override here.

## Inspect Activity and Results

Read the latest run's state and timing, then use run-history pagination for older results. A run can link to its conversation. **Results** can offer **Open chat**, **Open sync**, or **Open app**, depending on the saved target. A schedule existing or showing a next run is not execution evidence.

## Conflicts, errors, and deletion

If the schedule changed elsewhere, **Save changes** is blocked. **Discard my changes and load latest** replaces your draft with the saved server state; review it before editing again. A failed save keeps the draft for correction and retry.

For an eligible user-managed schedule, **Delete** removes that configuration after confirmation. Review the target first. Deletion and pausing are different actions, and neither implies that prior outputs were erased.

## Related guides

- [Scheduled Work](/docs/scheduled-work)
- [Artifact data and schedules](/docs/artifact-data)