Create a recurring Joule task

A scheduled Joule task saves a prompt and its working settings so Joule can repeat a marketing job on a schedule—or stay ready for you to run manually. Use one for recurring work that needs project context, files, or a flexible Joule workflow rather than one fixed AI Tool.

Scheduled tasks run inside Ampere. They are not a general social scheduler or outbound email sender, and you should review the output before publishing or acting on it.

Before you create the task

Prepare:

• A project that contains the relevant brief, brand context, or source files.
• A prompt that describes the outcome Joule should produce each time.
• Any stable instructions or attachments the recurring work needs.
• A schedule and timezone, unless you want a manual saved task.

Your organization needs enough credits when a run starts. A task can pause after repeated failures or when it cannot reserve the required credits.

Create a task from Scheduled Tasks

1. Open Scheduled Tasks and select New task.
2. Enter a recognizable Name and choose the Project where Joule should work and save results.
3. Write the recurring Prompt. Describe the deliverable, audience, inputs, and expected format.
4. Add optional Instructions for tone, sources, review criteria, or other stable rules.
5. Add attachments that should be available on every run.
6. Under When it runs, choose Hourly, Daily, Weekly, Monthly, or Manual.
7. For a recurring schedule, review the exact time and Timezone. Weekly schedules need at least one day.
8. Under How Joule runs this, review the model, effort, and machine settings.
9. Decide whether Joule may Use previous runs of this same task.
10. Choose the workspace members who should receive run-update emails.
11. Open Advanced settings if you need a description, a run limit, or a different repeated-failure pause threshold.
12. Review any available task permissions, then select Create task.

When creation succeeds, Ampere confirms Scheduled task created. If you granted an eligible permission, the confirmation can say that the task was created with standing permission. The task then appears on the Scheduled Tasks dashboard.

Write the prompt for repeatable work

Write the prompt as an instruction that will still make sense on a future run. Name:

• The result Joule should create.
• The project context or sources it should use.
• The time window, comparison point, or freshness rule when one matters.
• The required output format and review criteria.
• What Joule should do when evidence is incomplete.

Use Instructions for stable guardrails that apply across runs. Do not rely on a date or one-time detail that will be stale the next time the task runs.

Choose manual or scheduled mode

Choose Manual when you want a saved, reusable task without automatic runs. You can start it later with Run now.

Choose a recurring cadence when the work should run automatically. The stored timezone controls how the scheduled time is interpreted. Monthly schedules use the last day of shorter months when the selected day does not exist.

One-time work should usually stay in the current Joule chat instead of becoming a Scheduled Task.

Review Joule settings and previous runs

Model, effort, and machine settings apply to every run and can affect credit use. Defaults work well for many tasks; choose higher settings only when the recurring work needs them.

Use previous runs lets a compatible model inspect earlier runs of this same task when that helps compare changes or avoid repetition. If the selected model does not support that lookup, Ampere warns you. The task can still be saved, and the setting can become usable after you switch to a compatible model.

Set recipients and run limits

You can select current workspace members to receive succeeded, partial, or failed run updates. A task can store up to 100 recipients. Delivery also depends on each recipient's account preferences and Ampere's notification safeguards.

Use Run limit to stop the task automatically after a defined number of runs. Use Pause after repeated failures to control how many consecutive failed runs the task tolerates before pausing.

Understand task permissions and approvals

Some connected-account actions can offer Allow actions without asking. Grant only the exact account and action you expect the task to use.

Permission is scoped to the task and its current material configuration. A meaningful task change can require review again. If an eligible permission cannot be saved, the task is still created and asks for approval when it needs that action.

External actions that are not covered by valid permission can leave a run in Needs attention with the exact action waiting for approval. Destructive actions always require fresh approval.

Create a task through Joule

You can ask Joule in an interactive chat to set up recurring work. Joule presents a reviewable scheduled-task card with the proposed name, prompt, project, cadence, timezone, settings, and assumptions.

Review and edit the card before accepting it. A proposal is not a saved task: creation is complete only after the confirmation card returns the materialized task result. If creation fails, correct the card or dashboard settings and try again rather than assuming the task exists.