Schedule, Review and Pause Gab AI Tasks

Repeat a request you know how to check

Use Tasks for a recurring brief, reading prompt or report with clear inputs, timing and delivery. Test the request and inspect each result. A saved schedule is a configuration, not a guarantee that every future run will complete.

An actual scheduled brief and a focused rerun

Schedule a recurring Chat task, then adjust its instructions as plans change. This workshop example updates the start time from 09:15 to 10:30 while keeping the other facts.

1
2
3
4
5
6
7
8
9
10Facts:
- Cedar workshop
- Saturday at 10:30
- Introductory woodworking
- 12 adult places

Unknowns:
- Venue
- Price
- Registration link

1Using only these facts, return a brief with labels Facts and Unknowns. Facts: Cedar workshop, Saturday, 09:15, introductory woodworking, 12 adult places. Venue, price and registration link are unknown. Do not search, email or publish anything. Keep it under 90 words.

1
2
3
4
5
6
7
8
9
10Facts
- Workshop: Cedar
- Topic: Introductory woodworking
- Schedule: Saturday, 09:15
- Capacity: 12 adult places

Unknowns
- Venue
- Price
- Registration link

1. Set up the request and execution mode

Open Tasks and choose New task or a template. Complete Configure, Schedule, Email and Review. Name the task, supply instructions of up to 2,048 characters and choose Run using and the model.

• Work access and session limitsLearn more
• Create and test a botLearn more
• Bot settingsLearn more

2. Choose cadence, time and time zone

The web picker offers Once, Daily, Weekly and Monthly. Recurring tasks retain their saved time zone when opened on another device; new tasks start with the creating device’s zone. Review cadence, time and zone before saving, especially around daylight-saving changes.

• For Once, check the calendar date and time rather than only the hour.
• For Weekly or Monthly, check the selected weekday or day of month.
• Monthly schedules use local calendar dates. If the chosen day is unavailable, the occurrence uses that month’s final day. Check the intended occurrence for your schedule.
• Review the cadence, time and zone together. If no absolute next-run timestamp is shown, check your calendar and inspect Activity and Results after the expected occurrence.
• Allow time for scheduled processing and model execution after the chosen start time.

3. Review delivery before creating

Choose whether to enable email delivery. With it off, find results through the task’s Results action and conversation history. Review the request, model, schedule and delivery choices, then choose Create Task.

4. Inspect Activity and the actual result

Open the task, choose Activity and read Total Runs, Successful, Failed and Last run. Open View Results or use Results in the list. Compare the actual answer with the source facts; a success count does not prove that the content is correct. Run Now is a manual request and does not establish that the scheduler fired.

5. Revise the saved request and test deliberately

Edit the task’s instructions, choose Save changes and inspect the saved text. Name the specific correction and keep other facts stable. Run Now creates another chargeable request; it does not advance the recurring cadence. In the checked example, it also worked while the recurring schedule was paused.

1Using only these facts, return a brief with labels Facts and Unknowns. Facts: Cedar workshop, Saturday, 10:30, introductory woodworking, 12 adult places. Venue, price and registration link are unknown. Do not search, email or publish anything. Keep it under 90 words.

6. Pause future runs or remove an unwanted schedule

Turn off the task’s Enabled switch and confirm Paused. Reopen Tasks to check the saved state. Pausing future scheduling is separate from stopping work already running, and a deliberate Run Now can still execute. Deleting a result conversation does not delete its schedule. Remove the schedule itself when you intend to stop keeping it.

Review request access and usage

Choose an available model and Chat or Work mode, then review the current estimate. Scheduled runs use applicable credits; Work retains its Plus and task-capacity requirements. Find completed requests in Usage activity.

Task limits and failures

The inspected creation route limits an account to 20 undeleted task records, including paused ones. If creation is refused, review the schedules you intend to keep. Model access, credits, Work capacity and an unavailable bound conversation can also block a run. Inspect Activity and the actual error before retrying; repeated retries may create new usage.

• Check Enabled, the saved local time/zone and whether the expected occurrence is still ahead.
• Check model availability, current account access and credits.
• For Work, inspect active-session capacity and whether a bound task is already busy.
• Review failed-run details. The inspected worker disables a task after three consecutive non-deferred failures; resolve the cause before enabling it again.
• If an associated Work conversation was deleted, the schedule is retained but paused. Review its mode/binding before resuming.

Start with a request you can check

Try a small reading brief or meeting-action request with permitted inputs. Run it once and review the result before choosing a recurring schedule and delivery.

For a weekly report, name the reporting period, source location, measures and output format. Explain what to do when new data is missing, and make sure the scheduled run can access the intended source. For recurring research, ask for source links and changes since the previous period. The task checks at its scheduled time; it is not continuous monitoring.

1
2
3From these permitted notes: [NOTES], return a short weekly brief with Facts, Actions and Unknowns. Give each action only an explicitly supplied owner/deadline. Do not send messages or publish.
Revision: change only [ONE FACT]; preserve [DETAILS].
Check: compare every row with the notes before using the result.

Scheduled task questions

Timing, manual execution and successful content are separate checks.

Schedule a request you want to repeat.

Open Tasks, test a clear request and review the cadence, time zone and delivery before creating the schedule.