Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Gemini has two different automation features that people often call “tasks”: Tasks and Schedules in Gemini Spark, and scheduled actions in Gemini chat. They have different menus, eligibility rules, limits and failure modes. Identify which one you used first; applying scheduled-action advice to a Spark schedule (or the reverse) can hide the real problem.
This guide follows Google’s current Help documentation (accessed October 13, 2026). It covers missing controls, schedules that cannot be created or resumed, missed or late runs, time-zone surprises, connected-app failures and notifications that never appear.
First, identify the Gemini feature
Gemini Spark Tasks and Schedules
In Gemini Spark, a task is the goal, a schedule is the time or event condition that runs it, and a skill supplies reusable instructions and context. Spark has dedicated Tasks and Schedules views. Google explains skills separately in its skills documentation.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Scan for outdated or missing drivers - takes under a minute3Repair Windows errors before they cause bigger problemsSpark is available through Gemini mobile, the Gemini app on Mac and the Gemini web app, subject to account, plan and regional requirements. A Spark schedule can be paused, completed or ongoing, and it can be tested with Run now.
#1 Best Overall
Scheduled actions in Gemini chat
Scheduled actions are created from a Gemini conversation and managed under Settings & help → Scheduled actions or from the action’s chat. They are not Spark schedules. Google is still gradually rolling this feature out to personal Google Accounts, so an eligible account may not have the control yet.
| Feature | Where you manage it | Current documented limit | Most relevant checks |
|---|---|---|---|
| Gemini Spark schedule | Gemini Spark → Tasks → task thread and its schedules | 50 active schedules; 15 tasks running concurrently | Spark eligibility, schedule state, usage limit, concurrency, time zone and approximate timing |
| Scheduled action in Gemini chat | Settings & help → Scheduled actions, or the action’s chat | 10 active scheduled actions | Account rollout, Keep Activity, inactivity status, connected apps, execution and notifications |
The limits in this table are separate Google product limits documented in 2026 Help content; reaching one does not mean you reached the other.
If Gemini Spark or its schedule controls are missing
Check access before rewriting the prompt. Google currently requires all of the following for Gemini Spark:
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
- You are at least 18 years old.
- You use a personal Google Account, not a work or school account.
- Your account has Google AI Pro or Google AI Ultra.
- Keep Activity is turned on.
- You are in a supported country or region. Google lists Spark as unavailable in the European Economic Area, Nigeria, Switzerland and the United Kingdom.
- You are using one of the supported surfaces: Gemini mobile, the Gemini Mac app or the Gemini web app.
Review the current availability and requirements in Google’s Create and manage schedules for tasks in Gemini Spark help page. If any requirement fails, the Spark switch, Tasks view or schedule controls may not appear at all. A work or school account cannot be used for Spark even if that organization has another Gemini entitlement.
Check the account avatar before drawing conclusions. A browser can have several Google accounts signed in, and the account that owns a task may not be the one currently shown in Gemini. Sign out only if necessary; first switch to the account that created the task and reload the Spark interface. Also test the supported web, mobile or Mac surface rather than assuming that a missing control on one surface proves the feature is unavailable everywhere.
When you cannot create or turn on a Spark schedule
Use this order so that a missing control is not confused with a completed schedule or a capacity limit.
- Verify eligibility and sign-in. Confirm that you are in the personal account that owns the task, Keep Activity is on, your Google AI Pro or Ultra subscription is active, and your location is supported. If you recently changed accounts in the browser or app, switch back to the account where the task was created.
- Open the task and inspect its schedules. In Spark, open Tasks, select the relevant task thread, and review the schedule status sections. Look for an ongoing schedule rather than one marked paused or completed.
- Count active schedules. Google currently allows a maximum of 50 active Spark schedules. Pause or delete an existing active schedule before creating or resuming another when you have reached that cap.
- Check whether the schedule is completed. Google says a completed schedule cannot be edited or resumed. Delete it and create a new schedule instead.
- Complete every required field. A schedule made from a template needs a name, a run time and task instructions. A missing value can block creation even when Spark itself is working.
- Check whether Spark was disabled. Google says schedules pause automatically when Gemini Spark is turned off. Re-enable Spark, then return to the schedule and resume it if the control is available.
- Check subscription changes. Cancelling or downgrading to a plan without Spark access removes access to Spark tasks and schedules, but Google says the schedules are paused rather than deleted. Resubscribing or upgrading to an eligible plan restores access so you can resume them.
Do not treat a paused schedule as lost data. Its state is different from a completed schedule, which must be replaced. Before creating a replacement, inspect every existing schedule under the task thread; duplicate schedules can produce duplicate work and consume another active slot.
Why a Spark schedule did not run on time or run at all
Check capacity at the scheduled moment
Two limits can prevent an otherwise valid Spark schedule from running. Google says no schedule runs when 15 tasks are already running, and a schedule also does not run when the account has reached its Gemini Apps usage limit at that time. The concurrency number is a maximum of 15 simultaneously running tasks, not a daily allowance. Check both the task list and your account’s current Gemini usage.
A schedule can therefore be correctly configured yet fail only at a busy moment. Note the approximate time of the missed run and whether other tasks were active then. If a later manual run succeeds, that points toward timing, capacity or account state at the original moment rather than proving that the schedule definition was wrong.
Allow for approximate timing and traffic delays
Google states that Spark run times are approximate and may not occur at the exact moment a time or event condition is met. High traffic can delay a scheduled task. Therefore, Spark is unsuitable for a hard deadline such as an exact alert at a guaranteed second. Judge a run as late only after allowing for the documented approximation and a service delay.
Event conditions deserve the same caution as clock times. The condition can be met while service traffic is high, so the task may start later than the triggering event. Do not create several copies to compensate for a delay; first determine whether the original task eventually ran.
Use Run now as a diagnostic
For a new time-based schedule, open the schedule and select Run now. This tests whether the task can execute on demand. If it succeeds manually but not at the scheduled time, investigate the schedule’s active or paused state, its time zone, account limits and the approximate-timing rule. A successful manual run is useful evidence, but it does not prove that a future scheduled run will have capacity.
If Run now is unavailable, check whether the schedule is completed, paused or otherwise inactive before treating the absence as a service failure. If it runs but produces an unexpected result, the execution path is working and the next investigation should focus on the task instructions, skill context or connected data rather than schedule delivery.
Check the time zone anchored to creation
A Spark time-based schedule remains anchored to the time zone in which it was created, even if you travel. A schedule created in New York can therefore run at an unexpected local hour after you move to Los Angeles. Ask Gemini to edit the schedule using the new intended time zone, then inspect the resulting schedule rather than relying on your device’s current clock.
Record both the creation location and the intended new location when reporting a time-zone problem. Changing the phone or computer’s clock does not by itself rewrite the schedule’s stored time zone.
Inspect state after a plan or feature change
If a subscription downgrade or a temporary Spark switch-off occurred, the schedule may be paused automatically. Restore Spark access first, then verify that the schedule is ongoing. Do not create duplicates until you have checked the original task thread; doing so can consume the 50-active-schedule allowance.
When a scheduled action in Gemini chat is missing or stopped
Confirm separate eligibility and rollout
Google lists a personal Google Account, or a work or school account on a qualifying Workspace edition, with Keep Activity enabled. Availability for personal accounts is rolling out gradually, so an eligible account may still lack the scheduled-actions control. This rollout limitation is different from Spark’s regional and subscription requirements.
Because rollout is gradual, the absence of the menu is not necessarily caused by a bad prompt or a disabled action. Check the account type and Keep Activity first, then allow for the possibility that the feature has not reached that personal account yet.
Check the 10-action limit
Google currently permits 10 active scheduled actions in Gemini chat. If you have reached that feature-specific cap, deactivate or remove an action before creating another. Do not count Spark schedules toward this number.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Turn an inactive action back on
Go to Settings & help → Scheduled actions and inspect the action’s status. Google says an action may be turned off automatically because of inactivity. Turn it on again if the control is available, or open the action’s chat and manage it there. A missing notification does not by itself mean the action is disabled.
Look for an explicit inactive or off state rather than relying on memory that the action was once enabled. After turning it on, confirm that it appears among the active actions and that you have not exceeded the ten-action cap.
Reconnect the app the prompt needs
If the action depends on Gmail, Calendar, Google Workspace or another connected service, verify that the relevant app is linked to Gemini. Google says Gemini will ask you to connect an app when it is not connected. Complete that authorization before testing the action again; changing the wording of the prompt cannot replace a missing permission.
Connected-app access is a separate layer from schedule timing. An action can fire at the expected time but fail to produce the intended information if the required app was never connected or its authorization needs attention. Reconnect the specific service named in the prompt rather than assuming all Google services share one permission.
Separate execution from notification
The result of a scheduled action appears in the Gemini web app as an unread chat. A mobile notification may also be sent, depending on your phone’s notification settings. If the unread chat contains the result but no alert appeared, check Gemini’s operating-system notification permission and the app’s notification settings. Treat the absence of an alert as a notification problem unless the web chat is also missing.
Check the web result before recreating an action. Recreating it because a push alert was blocked can lead to duplicate actions and multiple responses. Execution and notification are related but not identical outcomes.
Understand when the response was prepared
Scheduled actions are prepared in advance. Google says responses without a Google AI plan may be prepared several hours before delivery, while responses with a Google AI plan may be prepared within the hour before delivery. Information that changes rapidly may therefore be out of date when the response arrives. This is an inherent timing limitation, not necessarily a failed action.
For fast-changing information, interpret the delivered response as something prepared ahead of the delivery time, not as a guaranteed real-time snapshot. If the response exists but is stale, that is different from an action that never executed.
Quick wins for a faster PC:
Clear out junk files and repair common Windows errorsFree Scan →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Repair Windows errors before they cause bigger problemsFix Now →What each symptom actually tells you
A missing Spark switch is primarily an access or availability question. A blocked schedule form points to required fields, a completed state or the 50-schedule cap. A schedule that exists but misses a run points to usage, concurrency, timing, time zone or traffic. For chat scheduled actions, a missing menu can be rollout-related, while an existing action that stopped is more likely inactive or at the ten-action limit. A result in an unread web chat with no phone alert is an operating-system notification issue, not proof that Gemini failed to run.
Keeping these layers separate prevents the most common troubleshooting mistake: changing task wording when the real issue is account eligibility, or reinstalling an app when the action actually completed in the web interface.
Fast triage by symptom
| What you see | First checks | Feature |
|---|---|---|
| Spark or its controls are missing | Personal account, age 18 or older, supported region and platform, Google AI Pro or Ultra, Keep Activity | Spark |
| You cannot create or resume a schedule | 50-active-schedule cap, completed status, and required name, run time and instructions | Spark |
| A Spark schedule did not run | Usage limit at run time, 15-task concurrency, paused state, approximate timing and high-traffic delay | Spark |
| A schedule ran at an unexpected local time | Time zone where it was created; edit it for the new time zone after travel | Spark |
| A scheduled action is missing or stopped | Gradual rollout, account type, Keep Activity, 10-action cap and inactivity auto-off | Gemini chat |
| An action needs Gmail, Calendar or another app | Confirm the relevant Connected App is linked and authorized | Gemini chat |
| The result exists but no alert appeared | Open the unread web chat, then check phone and Gemini notification permissions | Gemini chat |
A practical recovery sequence
When the symptom is unclear, work from the outside in:
- Identify whether the item is in Spark’s Tasks/Schedules views or in Gemini chat’s Scheduled actions page.
- Verify account type, plan, Keep Activity and regional or rollout availability for that feature.
- Inspect the item’s state: ongoing, paused, completed or automatically turned off.
- Check the feature-specific cap: 50 active Spark schedules, 15 concurrently running Spark tasks or 10 active chat scheduled actions.
- For Spark, verify the creation time zone and use Run now. For chat actions, verify required connected apps.
- Check whether the task executed in the web interface before diagnosing a missing notification.
- Retry only after correcting the identified condition, so you do not create duplicate schedules or consume another active slot.
What to record before contacting support
Write down the feature name, the account type, the plan, the schedule or action status, the intended time and time zone, and the approximate time you expected it to run. Note any usage, concurrency or limit message. For Spark, record whether Run now worked. For a chat action, record whether the required connected app was authorized and whether an unread result appeared on the web. This compact record lets support distinguish access, capacity, execution, timing and notification problems without requiring you to share sensitive task instructions.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →When the documented checks do not explain the failure
Public Help cannot show whether a particular account has received a gradual rollout, reached its live compute limit or encountered a temporary service incident. Record the feature, account type, schedule status, approximate run time, time zone and any limit message. Then report the persistent failure through Gemini Apps feedback or Google support. Include whether Run now worked, whether an unread result appeared on the web and whether the problem affects one schedule or every schedule. Those details distinguish execution, eligibility, capacity and notification failures without exposing sensitive task instructions.
For the authoritative, changing requirements and interface labels, consult Google’s Spark schedule help and scheduled-actions help pages.
Frequently Asked Questions
Why didn’t my Gemini schedule run on time or run at all?
First identify whether it is a Spark schedule or a Gemini chat scheduled action. For Spark, check that the schedule is ongoing, the account was below its Gemini Apps usage limit, fewer than 15 tasks were already running, and the schedule’s creation time zone is correct. Google says Spark run times are approximate and high traffic can delay them, so an exact-time miss is not automatically a configuration failure.
I can’t create or turn on a Spark schedule. What should I check?
Confirm Spark eligibility: age 18 or older, a personal Google Account, Google AI Pro or Ultra, Keep Activity enabled, a supported region and a supported Gemini surface. Then check the 50-active-schedule limit, required name, run time and instructions, and whether the schedule is completed. Completed schedules cannot be resumed; delete and recreate them.
What happens when I cancel or downgrade my Google AI plan?
If the new plan does not include Spark, Google says access to Spark tasks and schedules is removed and schedules are paused rather than deleted. Restore an eligible plan, reopen the original task thread and verify that the schedule is ongoing before creating anything new.
Why does a Spark schedule run at the wrong local time after travel?
Spark time-based schedules stay anchored to the time zone where they were created. Ask Gemini to edit the schedule for the new intended time zone and inspect the updated schedule. Changing your device clock or traveling does not automatically change the schedule’s stored time zone.
Why is Scheduled actions missing from Gemini chat?
Scheduled actions are separate from Spark. They require Keep Activity and either a personal Google Account or a qualifying Workspace account. Google is gradually rolling the feature out to personal accounts, so an eligible personal account may not have the control yet.
How many Gemini automations can I have?
Google currently documents three separate limits: 50 active Spark schedules, 15 concurrently running Spark tasks and 10 active scheduled actions in Gemini chat. These limits are feature-specific and should not be added together or counted interchangeably.
Free tools Windows power users keep installed
One-click scans. No signup required.
The action ran, but I received no notification. Did it fail?
Not necessarily. A scheduled-action result appears as an unread chat in the Gemini web app; a phone alert depends on device and app notification settings. Open the unread chat first. If the result is there, check operating-system and Gemini notification permissions instead of recreating the action.
Why is a scheduled-action response out of date?
Google says scheduled actions are prepared in advance: responses without a Google AI plan may be prepared several hours early, while responses with a plan may be prepared within the hour before delivery. Rapidly changing information may therefore not be current when the response arrives.
The Bottom Line
Start by naming the feature: Gemini Spark schedules and Gemini chat scheduled actions have different access rules, menus and limits. Then check eligibility, status, feature-specific capacity, timing and connected apps in that order. For Spark, remember the 50-active-schedule cap, 15-task concurrency limit, creation-time time zone and approximate run times. For chat actions, check gradual rollout, the 10-action cap, inactivity and connected apps. Finally, verify the web result before blaming notifications, and report persistent failures with the feature, status, time zone and limit details.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
