# Follow-ups > Ask June to check back at a time and act if nothing moved. Reminders, repeating schedules, the Schedules page, and what June does without asking. Source: https://www.dearjune.ai/docs/follow-ups Ask June to check back on something at a time, and to act if nothing moved. At that time it runs the instruction you saved and posts back in the same thread: it looks at what you pointed it to, and if the thing is still stuck, it brings the draft, reminder or question you asked for. 1. Say what to check, when, and what to do if nothing moved. If the check has to read your tools or the web, ask June to turn them on for it. 2. Check the confirmed time, time zone and instruction on the **Schedules** page. Include the source and what counts as a change; a work run does not reread this conversation. 3. At that time, June posts its result in the thread where you asked. Web and app delivery also requests a device notification; notifications must be enabled. If the thing moved, it tells you; if not, it does what you asked. > Example prompt: On Friday at 9, check my mail for a payment from Meyer GmbH on invoice 2026-041, with the integrations toolset on. If nothing came, draft a firmer second reminder Name a time zone if it matters ("9:00 Berlin time"). Times work to the minute. ## What a check can use A check or schedule June sets up from chat runs without your tools by default: it answers from its instruction and what June remembers, not from your mail, files or the web. Ask June to turn on the toolsets it needs, by name: - `integrations`: the tools on your **Integrations** page, such as your mailbox, Microsoft 365 or Notion - `web`: web search - `documents`: Google Docs, Slides, PDFs and images in your Google Drive - `terminal`: June's sandbox, including GitHub as you, wherever the schedule was set up On the **New schedule** form, list them under **Enabled toolsets**. [How schedules run](/docs/how-june-works/schedules#what-a-run-can-use) has the rest of what a run can use. Before leaving a check to repeat, choose **Run now** and review the result under **Open history**. If it cannot read the source, reconnect the account or correct the instruction, then try again. A schedule keeps its timetable after a failure until you pause it. ## Reminders A reminder is a message June brings back at the time you named. It does no new work when it fires; for a check, ask for a follow-up as above. > Example prompt: Remind me Friday at 9 to send the invoice to Meyer GmbH Say when in plain words: a time, a day, or "in two hours". June posts the reminder in the thread where you asked and notifies your devices. ## Schedules A schedule repeats a piece of work: "every Monday at 7", "every 30 minutes", "on the 25th of every month". Each time it runs, June reads, searches or checks what you described, with the toolsets you turned on for it, and posts what it found. > Example prompt: Every Monday at 7, check the invoices spreadsheet in my OneDrive and tell me which ones are overdue, with a reminder drafted for each. Turn on the integrations toolset for it For checks that should only report a result, say what counts: “Only tell me when a new reply arrives; otherwise stay quiet.” You can ask June to change an existing schedule this way too. When a run finds no qualifying result, it can finish without posting a message or sending a device notification. If June cannot perform the check, it reports the problem. A follow-up, reminder or schedule replies in the thread you asked in. If June is in your Slack workspace, ask for Slack and it posts there instead. ## The Schedules page The **Schedules** page lists everything June does for you at a set time: what needs attention because its last run failed, what is coming up next, what is paused, and what is already done. Each schedule's menu has: - **Run now**: run it once, now. - **Pause** and **Resume**: stop it until you resume it. Resuming picks a new next run. - **Open history**: its past runs. - **Delete**: it stops and leaves the list. This cannot be undone. If creating a schedule fails, the form shows an error and keeps your entries so you can correct them and try again. You can also ask June in chat to list, change, pause or remove a schedule. In an organization chat, June manages your schedules in that organization. Public threads show only schedules created in public threads; your private chats and Slack DMs stay private. **New schedule** opens a form for setting one up by hand. [How schedules run](/docs/how-june-works/schedules) has the exact rules: time zones, missed runs, who pays and what a run can use. ## What June does on its own, and where it stops June works on what you ask, in the thread where you ask. Work it does later is a follow-up, reminder or schedule you set. **June can:** - read and search the web, the files you attach, and the tools you connected on the **Integrations** page - draft replies, messages and documents for you to send or use - run code in [its sandbox](/docs/how-june-works/sandbox), its own workspace in the cloud - save what it learns about you as [memories](/docs/memory) - leave comments on GitHub when you ask, as you, in your own and an organization's chats and in Slack - start a separate thread for part of the work, on the web and in the app **June stops short of:** - **sending mail in these examples.** They ask for drafts. Gmail can also send, following your [approval settings](/docs/settings/approvals); IMAP and Outlook keep it as a draft. - **changes that need approval.** In chat, June asks before making a change unless a permission you already granted covers it. A scheduled run cannot complete an integration step that needs confirmation; ask it to report the proposed change for you to handle in chat ([connection limits](/docs/how-june-works/connections#a-step-that-needs-your-confirmation)). - **commands that could do damage.** Its sandbox refuses commands such as wiping a disk or running a script piped straight from the internet ([the full list](/docs/how-june-works/sandbox#commands-june-refuses)). ## What follow-ups do not do - A schedule does not run more often than once a minute. - A schedule cannot set up further schedules. - A check does not read your tools unless you turned its toolsets on.