Schedule recurring AI tasks in AgReady

What a scheduled task does

AgReady can submit an instruction to a session on a schedule. This is useful for recurring reviews, summaries, or checks that you already know how to perform in a normal session.

The schedule starts work; it does not guarantee a useful result. The target session still needs a working model, appropriate tools, access to its inputs, and any required approvals.

Prepare the target session

Run the task manually first. Confirm the inputs, output format, allowed actions, and where you will review the result.

Keep recurring instructions bounded. A daily review should say what to check, what to return, and what must not happen automatically. Avoid scheduling external publication or other sensitive actions merely because generating a draft worked.

Create a timer

1. From a session, open the account menu and choose Settings, then Operations → Triggers.
2. Select New trigger and keep the type as Timer.
3. Give it a recognizable name and select its target session.
4. Write the activation message: the instruction the session receives each time.
5. Choose the timing mode described below.
6. Review its enabled state, context setting, expiration, and Fire limit, then save.

• Interval time: repeat after a specified number of seconds, minutes, or hours.
• fixed time: run daily, weekly, or monthly.
• Absolute time: run at a specified Unix-millisecond timestamp; use a Fire limit of 1 for a one-time trigger.

The Key is generated by the interface and identifies the trigger.

Time-zone note: In the currently documented implementation, fixed-time schedules use UTC+8. Do not assume that entering 09:00 means 09:00 in your browser’s local time. Check the next-run display before relying on the schedule.

A Fire limit of 0 means unlimited activations. Start with a small limit when checking a new recurring workflow. The limit counts successful session activations, not verified task completions.

Check what actually happened

The trigger list shows its status, schedule and Next run. Open its details for the last-fired time, fire count and latest error, or Execution history for individual attempts and reasons.

• Triggered: the session was activated; inspect its conversation and output.
• Deferred: the target may already be running or waiting for approval or user input.
• Trigger error: inspect the recorded reason.
• Unconfirmed: do not assume either success or failure.

Execution history covers recorded attempts, not reconstructed activity from before the history feature was enabled.

Judge the task separately: Did the session use the intended inputs, produce the requested output, and respect its boundaries?

Edit, disable, or remove a schedule

Use Edit to change the instruction or schedule. Use Disable to prevent future scheduled or external activations while retaining the definition. Use Enable to resume eligible future activations, or Delete when the trigger is no longer needed.

Disabling or deleting a trigger does not withdraw an input already accepted by a session. If work has started, inspect the target session and use its run controls as needed. Stopping the current run does not automatically disable the recurring trigger.

Schedules run on the AgReady server. The service must be available, and stored schedules do not imply that every missed interval during downtime will be replayed.