- Help Center
- Scheduled tasks
- Review scheduled Joule runs, outputs, approvals, and emails
Review scheduled Joule runs, outputs, approvals, and emails
Learn how to review scheduled Joule run statuses, outputs, approvals, credits, recipients, and email delivery.
Last verified about 21 hours ago
Each run of a scheduled Joule 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 Joule 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
- Open Scheduled Tasks.
- Find the prompt task you want to review. You can search, filter by status or type, and sort by recent runs.
- Select the task row or choose View details from its actions menu.
- Select Runs in the task detail sheet.
The Runs tab shows the total run count and lists manual and scheduled runs. Each row can include the run number, status, scheduled time, completion time, a short Joule summary, credit usage, approval details, and saved output names.
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:
| Status | What it means |
|---|---|
| Pending or Queued | The run is waiting to start. A run may also show Waiting while other scheduled Joule runs finish. |
| Running | Joule is working. Active runs refresh automatically. |
| Retrying | Joule will try again when the session is available. |
| Needs attention | Joule prepared an action that requires approval before the run can finish. |
| Succeeded | The scheduled run completed successfully. |
| Partial | The run saved useful work but did not complete every intended action. This can happen when an approval is denied, expires, or cannot be completed. |
| Failed | The run could not complete. Review its message and any saved outputs before deciding whether to run the task again. |
| Skipped | The run did not proceed. Review the message for the reason. |
| Canceled | Someone stopped the queued or active run. Past run history remains available. |
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 Joule session and saved outputs
Select Open on a run to inspect the Joule session when you have access. You can also select the run row itself unless you are interacting with a button, link, or approval control inside it.
A run can show several kinds of saved work:
- A short preview of Joule's final response.
- Report or Project Asset links that open the saved asset in its project.
- Other output names recorded for the run.
Output access follows the existing project and session permissions. If the run belongs to another task owner and you cannot open its Joule session, the row 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. Joule 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 Joule 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 Joule 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, a completed run can show Used n credits. Select it to see the available breakdown:
- Joule AI usage.
- Catalog tools used during the scheduled run.
- Scheduled run total.
- Full chat total when later assistant turns added work to the same chat.
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:
- Choose Manage email recipients.
- Select current workspace members who should receive future completed-run emails.
- 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 workspace.
- The recipient's email is missing or unverified.
- The recipient or workspace 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:
- Read the run status and its message.
- Opened the Joule session or available saved outputs.
- Resolved every pending approval you are authorized to decide.
- Waited for the credit total to settle when usage is still updating.
- Confirmed the recipient list if the team expects run update emails.
Keep a human review step before publishing or relying on scheduled Joule output, especially when the run used public data, proposed an external action, or completed only part of the requested work.
Was this article helpful?
Related articles
Learn how to read credits remaining, current-period usage, historical usage, grants, and background AI allowance.
Learn what Joule resume and recovery can do after interruptions, what to review, and when to retry or ask for help.
Learn how to review Joule outputs, download files when available, and ask Joule to bundle multiple outputs as a zip.