Scheduled Tasks

Scheduled tasks allow your Brand to build deliverables on a recurring timetable without you being present. Each run begins a new session in your Stories bar, applying your master brand brief automatically.

​

What it is

A scheduled task is a standing instruction in your Brand to invoke a Computer at set times — every weekday morning, weekly on Mondays, or at fixed intervals. When a scheduled time arrives, Nutgraf creates an independent session in your Stories bar and executes the build using a computer. Because scheduled runs execute unattended, each task carries a self-contained request that can be evaluated on any given day. The run automatically inherits your master brand brief, voice clone, and digital presenter setup from the Brand workspace.

​

How to use it

​

1. Describe what you want scheduled

Open your Brand conversation and state what you want built, how often, and in which time zone. For example, tell the Brand agent: “Find the five biggest AI announcements of the past 24 hours and make a 60-second video every weekday morning at 8am Eastern.” State your requirements directly in natural language.

​

2. Confirm the schedule details

Your Brand agent confirms the four core details before creating the task: the Computer (Creative Studio or Product Development), the self-contained request, the schedule frequency, and your local time zone. For times set on the hour or half-hour (such as 8:00am), the agent suggests starting a few minutes earlier (such as 7:52am) to prevent platform queuing delays.

​

3. Review the confirmation

Review the one-line summary provided by the agent. Reply to confirm the prompt. Nutgraf registers the schedule and reports the next three upcoming run times in your local time zone.

​

4. Manage existing schedules

Manage your scheduled tasks at any time directly through the Brand conversation:

• List: Ask “What tasks are scheduled?” to view all active and paused tasks.
• Pause and resume: Say “Pause the daily AI video” or “Resume the Monday briefing”.
• Run now: Say “Run the weekly video now” to trigger an immediate execution without altering the recurring schedule.
• Edit: Say “Change the daily video to 9am London time”.
• Delete: Say “Delete the daily AI video”. Completed past runs remain permanently in your Stories bar.

​

What You Need to Know

​

Session autonomy and Stories integration

Each scheduled execution opens a new, independent session tab in your Stories bar. The session displays an amber icon while running and turns green when the deliverable is ready. You can open any completed run to review the draft, download media, or request revisions through conversation.

​

Brief inheritance

Scheduled runs always load the latest master brand brief from your Brand workspace. If you update your brand guidelines, digital presenter, or tone of voice, all subsequent scheduled runs immediately adopt those updates. Past completed runs remain untouched.

​

Approval modes

Tasks inherit your account’s approval setting:

• Ask mode (default): If a step requires approval (such as script sign-off), the session pauses and displays a badge dot on its story icon, waiting for your input.
• Auto mode: The Computer completes the build end to end without waiting for manual sign-off.

​

Overlap and late run bounds

If a previous run is still in progress when the next fire time arrives, Nutgraf skips the new run to prevent duplicate work. If system downtime delays a scheduled fire by more than one hour, the run is recorded as missed and Nutgraf advances to the next interval. A task never executes back-to-back duplicate runs on recovery.

​

Minimum intervals

The shortest permissible interval for a scheduled task is one hour. High-frequency polling (such as every 15 minutes) is not supported.

​

Tips

• Write self-contained requests. Use relative time windows like “announcements in the past 24 hours” rather than “today’s news”, ensuring every run understands its scope independently.
• Accept off-the-hour suggestions. Starting at 7:52am instead of 8:00am avoids common platform traffic spikes and produces faster turnaround times.
• Start in Ask mode. Keep new recurring tasks in Ask mode for the first few runs to verify output quality before enabling Auto.
• Use Run Now for verification. After creating or editing a task, trigger an immediate execution with “Run it now” to verify the deliverable before the next scheduled fire.

​

Frequently Asked Questions