Review prompt task runs, outputs, approvals, and emails

Each run of a prompt task keeps its own status, timing, output summary, credit total, and any approval history. Open the task's Runs tab when you want to check what happened, review saved work, or respond to an action that needs your approval.

Before you start

You need access to the Scheduled Task and its private run details. Some output links and Ampere sessions are available only to people with access to the owning project or session. Selecting someone as an email recipient does not give them access to private task inputs or run output.

Open a task's run history

1. Open Scheduled Tasks.
2. Select the Tasks tab.
3. Find the prompt task you want to review. You can search, filter by status or type, and sort by recent runs.
4. Select the task row or choose View details from its actions menu. The task opens on its own page.
5. Select Runs.

The Runs tab shows the total run count and pairs a list of manual and scheduled runs with a reading pane for the run you select. The newest run is selected for you. Each row in the list carries the run number, status, time, a short preview of Ampere's answer, and a count of what the run produced. The reading pane holds the rest: the full result, outputs, approvals, timings, and credits.

Use the status filter to narrow the list. Available filters include Running, Succeeded, Failed, Needs attention, Pending, Queued, Retrying, Partial, Skipped, and Canceled.

Understand the run status

Use the status and message together:

If a run is still active and you have permission, you can select Cancel. Canceling stops queued or active work for that run without removing past run history.

Open the Ampere session and saved outputs

Select any run in the list to open it in the reading pane. Choose Open in Ampere to inspect the full Ampere session when you have access.

The reading pane leads with Ampere's final answer, formatted the way Ampere wrote it. A long answer is shortened to a comfortable reading height; select Show more to read the rest and Show less to collapse it again. When a run's full response is no longer available, the pane shows the stored preview instead and says so.

Below the answer, a run groups what it produced:

• Deliverables are the finished files the run set out to create.
• Saved to project lists the assets Ampere saved into the project library, including reports. Select one to open it in its project.
• A line such as "10 working files stayed in the session workspace" counts the scratch files Ampere used along the way. These are counted rather than listed, so they do not crowd out the real output.

Only assets saved to a project have a page to open. Deliverables are shown by name.

Output access follows the existing project and session permissions. If the run belongs to another task owner and you cannot open its Ampere session, the reading pane explains that the owner must open it. A visible output name is not a new access grant.

For a partial run, review the saved output before rerunning the whole task. Ampere can preserve drafted work even when a later external action is denied, expires, or cannot be completed.

Respond when a run needs attention

A Needs attention run includes an Approval needed panel. Review the information shown for each proposed action:

• The action or tool name.
• The connected service and account label.
• The safe preview of what Ampere proposes to do.
• Whether the request is pending or already resolved.

Choose Approve only after the account and proposed action match what you expect. Choose Deny when you do not want the action to proceed. Denying closes the run as partial after all pending requests are resolved, while keeping the drafted work in the run's outputs.

Some eligible actions also offer Allow this task to do this automatically next time. Select it only when you want that exact task to reuse consent for the same connected account, action, scope, and material task setup. If the task changes in a meaningful way, future scheduled approvals require confirmation again.

Actions that do not support reusable consent show One-time approval only. Destructive scheduled actions always require a fresh one-time decision.

An approval can expire before you answer, or an approved action can expire or fail before Ampere finishes it. In each case, the run keeps the drafted work and explains the outcome. Review the saved output, then decide whether to retry in a new run.

Review run credits

After usage is confirmed, the run's Credits row shows a total such as n credits. Select it to see the available breakdown:

• Ampere AI usage.
• Catalog tools used during the scheduled run.
• Scheduled run total.
• Full chat total when later agent turns added work to the same session.

You may briefly see Credits settling... after a run completes. Wait for the total to finish updating instead of treating a missing total as zero usage.

Background AI usage is tracked separately and is not included in the scheduled run total shown in this popover. Reviewing run history, outputs, and settings does not spend credits.

Choose who receives run update emails

Task owners can manage run update recipients from the task's actions menu:

1. Choose Manage email recipients.
2. Select current Organization members who should receive future completed-run emails.
3. Select Save recipients.

You can select up to 100 recipients for a task. Saving an empty selection means no run-result email will be sent. A member without a verified email can remain selected, but that run records an email-unverified skip.

Eligible Succeeded, Partial, and Failed runs can generate an update email for selected recipients. The email can include run timing, a summary, output counts or names, approval attention, and an auto-pause notice when relevant. It links back to the run and notification controls; recipients still need normal Ampere access to open private content.

If a run update email does not arrive

Email delivery is not guaranteed. A selected recipient may not receive an email when:

• The task has no recipients selected.
• The recipient no longer belongs to the Organization.
• The recipient's email is missing or unverified.
• The recipient has turned off the relevant email notification.
• Delivery is suppressed after a hard bounce or spam complaint.
• The task is not eligible for execution, a notification limit applies, or delivery encounters a temporary or final error.

Review the run in Ampere first; the run history is the source of truth for status and saved work. Then confirm the task's current recipient list and the recipient's notification settings. Do not assume the run failed only because an email was skipped or delayed.

Confirm your review is complete

Before leaving the run, confirm that you have:

1. Read the run status and its message.
2. Opened the Ampere session or available saved outputs.
3. Resolved every pending approval you are authorized to decide.
4. Waited for the credit total to settle when usage is still updating.
5. Confirmed the recipient list if the team expects run update emails.

Keep a human review step before publishing or relying on prompt task output, especially when the run used public data, proposed an external action, or completed only part of the requested work.