Schedules

A schedule is a task the agent runs by itself, without you: every morning, every hour, on a given day, or once after some time.

#Create one

Ask in chat, in plain words, answering three questions: what to do, when, and where to send the result.

• "Every weekday at 9:00 New York time, gather news about our market from these five sources and send me the top five as a list in Telegram."
• "Every Monday at 10:00, make a sales report from the latest export in sales/ and save it to reports/."
• "In 20 minutes, remind me to call the supplier."

The agent turns this into a schedule, confirms when the first run will be, and every run then happens in the same project where you asked.

#Where the results go

• Every run reports into a chat of its own, named after the task and the day: Morning review · Oct 1. Runs of one task on the same day share that chat. In the sidebar these chats have a clock icon; the chat where you set the task up stays an ordinary conversation.
• If you asked, also in Telegram (the connected bot) or in a channel. The report says which chat it comes from, and answering it — or just writing next — continues that chat, with the report in it. See Telegram.
• Files the task makes are in the project, in the Files panel.

#Checks that stay quiet

A task that checks something often - new listings, a price, a tender search - finds nothing new most of the time. Such a task can stay silent: when a run has nothing to report, nothing is sent to Telegram, and its chat gets one line saying there was nothing new. The Watch listings, prices and tenders card sets its task up this way. There is no limit on how many scheduled tasks a workspace keeps.

#View, change, cancel

Settings → Schedules lists every task in the selected scope: what it does, its schedule, the next and last run, how many times it ran and whether it is enabled. You can also pause and resume a task, delete it or change its time here.

The easiest way is through the chat:

• "Show my schedules."
• "Move the morning digest to 8:30."
• "Make the digest include the dollar rate too" — you can change what a task does, not only when.
• "Cancel the supplier reminder."
• "Pause the digest until I am back from holiday" and, later, "resume the digest" — a paused task stays in the list and does not run.

If the task lives in another project or chat, the agent finds it.

#A task that cannot run

Sometimes a run cannot be carried out: the model's limit for the workspace is reached, or the disk is full. Left alone, such a task would be turned away every time it fires, and tell you so every time. So Eggent counts:

• The first refusal reaches you as the run's report, with the reason and what to do.
• The next ones are kept in the task's chat for that day and are not sent to Telegram again.
• On the third in a row the task is paused: you get one message saying so, with the reason, and the task shows paused by Eggent in Settings → Schedules.

A run that ends in an error is counted the same way, a little more patiently: it is announced once, and after five in a row the task is paused too. A good run clears the count.

Once the reason is dealt with, resume the task in Settings → Schedules, or ask the agent: "resume the morning digest". Nothing is deleted by a pause, and the count starts again after a resume.

A scheduled run's own report cannot create, change or delete tasks. Nobody is there to ask, so only you can — in a chat of your own or in Settings → Schedules.

#How time is written

The agent understands time in words and stores it in one of these formats:

#Reliability

• The cloud wakes the workspace for a run. Even if the workspace has gone to sleep, it wakes a couple of minutes before the task. See Sleep and wake.
• Missed runs are not repeated. If the workspace was off at the moment (your own server was rebooting, say), the task runs at its next scheduled time.
• A task spends balance like an ordinary message. Frequent tasks on a strong model use noticeable credits: for routine work pick a cheaper model in the project settings.
• A task runs alone. Nobody is there to answer a question during a run, so word the task so the agent has nothing to clarify.