I have set up a scheduled task to organize my Gmail “Promotions” tab every morning at 5:00 AM. I have configured the instructions to use “@gmail” so the task can call itself.
The issue is that while the task works perfectly when I trigger it manually, it consistently fails when the automated schedule attempts to run it. I have attached screenshots of the error message I receive each morning.
To troubleshoot this, I have already attempted the following:
Reconnecting the plugin multiple times.
Adjusting the instructions to reference “@gmail” and “@Gmail.”
Explicitly calling “@gmail” within the active chat conversation.
Adjusting plugin permissions to test different levels of restriction.
Despite these efforts, the task fails to execute autonomously. My goal is for this task to run daily at 5:00 AM to organize my promotions, apply the appropriate labels based on my instructions, and provide a summary report.
Any feedback or suggestions on how to resolve these automated trigger failures would be greatly appreciated. Thanks for the help!
I tested a Gmail-based scheduled task and it did access Gmail automatically. ChatGPT created it as an Email Monitor under Monitoring, set to run hourly (for me, but frequency can be chosen) and it notified me when a relevant email arrived. So unattended Gmail access itself is supported.
Your error specifically says the Gmail connector is unavailable in the automated execution context, so changing @gmail capitalization probably won’t resolve it. Could you try creating a new Monitoring task from scratch with a read-only instruction first, for example, “At 5:00 AM, check my Gmail Promotions tab and send me a summary”?
I have set up a scheduled task to organize my Gmail “Promotions” tab every morning at 5:00 AM. I have configured the instructions to use “@gmail” so the task can call itself.
The issue is that while the task works perfectly when I trigger it manually, it consistently fails when the automated schedule attempts to run it. I have attached screenshots of the error message I receive each morning.
To troubleshoot this, I have already attempted the following:
Reconnecting the plugin multiple times.
Adjusting the instructions to reference “@gmail” and “@Gmail.”
Explicitly calling “@gmail” within the active chat conversation.
Adjusting plugin permissions to test different levels of restriction.
Despite these efforts, the task fails to execute autonomously. My goal is for this task to run daily at 5:00 AM to organize my promotions, apply the appropriate labels based on my instructions, and provide a summary report.
Any feedback or suggestions on how to resolve these automated trigger failures would be greatly appreciated. Thanks for the help!
I created a brand new schedule using the chat feature in the “Schedule” tab and provided all the necessary instructions. This time, instead of calling “@gmail,” I instructed it to “Use Gmail to review my…”
It worked perfectly yesterday, as shown in the attached screenshot. However, this morning I woke up to this error message: “That requires live access to your Gmail account through the Gmail connector.” I haven’t changed any settings, permissions, plugins, or connectors, so I am curious what I might be doing wrong.
P.S. I am not sure why my previous post was closed, but this is clearly a bug that needs to be addressed for scheduled tasks to function properly.
It is strange that the same task successfully accessed Gmail yesterday, but then claimed it needed live Gmail access today, especially since you didn’t ´change anything. Since it worked once, the prompt wording itself doesn’t seem to be obvious problem.
Have you tried selecting Run now on the same task? If that succeeds, could you temporarily schedule it to run every hour to see whether the Gmail-access error occurs consistently or only on some automated runs?
Since Run now completes the same task successfully, your prompt and Gmail connection appear to be working. Combined with the successful automatic run yesterday, this seems to be an intermittent problem affecting the scheduled execution rather than something you are doing wrong.
Unfortunately, I don’t know of a user-side setting that would fix that. I suggest reporting it to the Support and including the failed scheduled run time, the successful Run now result and both screenshots, as that comparison should be useful for investigating the issue. You contact them through Help.
I’m having a similar problem when calling plugins in scheduled tasks (the plugins in my case are Google Drive, Spreadsheets, and Trello). I included references to them with @ at the start of the task instructions. The task runs fine when triggered manually, but I get messages similar to the following when the task is triggered according to the schedule:
"I’m not able to truthfully report that I performed this run.
Your requested workflow requires reading and updating Google Docs, Google Sheets, and Trello, performing web research, moving/updating Trello cards, and logging the run in the Worker agent log. In this chat, I don’t currently have access to the necessary connector functions to carry out those write operations end-to-end.
Rather than fabricate a result, I’ll state the specific blocker:
I cannot verify and update the Worker agent log in Google Sheets.
I cannot update Trello cards, notes, checklists, or move cards between lists.
I cannot update the linked Google documents as required by the charter.
Therefore I cannot honestly claim that the run has been completed.
If those connector functions are available in the environment (as they were in earlier runs), I can execute the workflow; otherwise I won’t invent completion or claim changes that were not actually made."
