Skip to content

Scheduled Jobs in Explore ​

A scheduled job repeats an Explore request on a schedule. You set it up by asking in a thread, for example "every Monday at 8 AM, send me overdue tickets by client". Each run takes place in that thread, as you, with nobody watching, and posts its result there.

Scheduled jobs are available to users with the Manager role or higher on every plan that includes Explore. You create them from Explore in the Junto web app, not from Slack or Teams.

How It Works ​

  1. Ask in an Explore thread. Describe what to do and when, including your timezone. You can also click the Schedule a recurring job play on the Explore home page and fill in the blanks.
  2. Review the draft. The agent proposes a name, the instruction each run will follow, the schedule and timezone, and any tools the runs may use without asking. It asks for your timezone if it doesn't know it.
  3. Confirm the approval card. The card shows the schedule, the timezone, and every tool that will run without asking, with where it may act. Creating a job, or changing it by asking in its thread, always needs your own confirmation. Your tool policies can't make this approval automatic.
  4. Let it run. A Scheduled job card appears beside the thread and the first run starts at the next scheduled time.

Write a complete instruction

Each run sees only the job's instruction and the thread, so name the sources, the companies, and where the result should go. "Every weekday at 7 AM Eastern, list Contoso's offline servers in NinjaOne and post the list to the Updates channel" works better than "check the servers".

Limits ​

LimitValue
Jobs per userUp to 10
How often a job can runAt most once an hour
Jobs per threadOne. Start a new thread for another job.
Pre-approved tools per jobUp to 25
ScheduleAny recurring pattern of minutes, hours, days, and months, read in the timezone you choose

What a Run Can Do ​

A run is an ordinary Explore turn without anyone watching. It runs as you: the same integrations, companies, and permissions, plus your own personal connections.

  • Reads run as they do in any conversation.
  • Pre-approved tools run without an approval prompt, but only against the targets you approved. If you pre-approved creating documentation for Acme Corp, a run can create documentation for Acme Corp and nowhere else. A call aimed at any other target is refused.
  • Anything else that needs approval is not run. The run carries on with what it can do and says in its reply what it skipped and why. To allow that action in future runs, ask in the job's thread to pre-approve it, then confirm the change.
  • A run never waits for an answer. It doesn't ask you questions and doesn't create or change scheduled jobs.

What Can Be Pre-Approved ​

Pre-approval removes the confirmation prompt for one tool in one job's runs. It never loosens your organization's stricter rules:

  • Tools that only read don't need pre-approval.
  • Tools that must always be confirmed by a person can't be pre-approved.
  • Tools set to Escalate in your tool policies, and tools your role can't use, can't be pre-approved.
  • If an admin later switches a pre-approved tool off or sets it to Escalate, runs refuse it.
  • A Per session grant from one of your conversations doesn't carry into a scheduled run. Runs use only what you pre-approved for the job.

Where Results Go ​

Each run posts in the job's thread. A divider reading Scheduled run with the date and time marks where each run starts, followed by the agent's reply. The reply opens with a one-line result, which also appears as the run's summary under Recent runs on the job card.

To send results somewhere else, such as your team's Updates channel or a direct message to a teammate, say so in the instruction and pre-approve the tool that sends it. See Posting from Explore.

Managing Jobs ​

You see and manage only the jobs you own.

The Job Card ​

A thread with a job shows a Scheduled job card beside it:

  • The job's name and status: Active, Paused, or Stopped.
  • Runs -- the schedule and its timezone.
  • Next -- the next run, in your own timezone.
  • Posts to -- this thread.
  • Pre-approved -- each tool that runs without asking, with where it may act.
  • Recent runs -- each run's time and result. Click a run to jump to it in the thread.
  • Run now, Edit, Pause / Resume, and See all scheduled jobs.

Collapse the card to a tab on the right edge that shows the next run time, or Last run failed. On a phone, the card starts collapsed.

The Scheduled Tab and Next Up ​

Explore's thread list has two tabs, Threads and Scheduled. The Scheduled tab lists each of your jobs with its schedule and next run; click one to open its thread.

When you have jobs, the Explore home page also shows Scheduled · next up: the next three jobs with their schedule, next run, last run, Run now, and a pause or resume button. View all opens the Scheduled tab.

Editing a Job ​

The simplest way to change a job is to ask in its thread, for example "move this to Tuesdays at 9". The agent updates the job after you confirm the card.

You can also click Edit on the job card. Edit scheduled job has these fields:

FieldDescription
NameShown on the card and in the Scheduled list.
Instruction (Markdown)What each run does.
Schedule (cron)A five-field cron expression, for example 0 8 * * 1 for Mondays at 8:00.
TimezoneThe timezone the schedule is read in, for example America/New_York.
Runs without askingThe pre-approved tools. You can remove one here.

To add a pre-approved tool or change where one may act, ask in the thread. You confirm it there.

Pausing, Resuming, and Running Now ​

  • Pause stops future runs. Resume schedules the next run from now.
  • Run now starts a run immediately. It is unavailable while a run is in progress.
  • If a run is still going when the next one is due, that scheduled run is skipped.

Deleting a Job ​

Click Edit, then Delete job and Confirm delete. A job can't be deleted while a run is in progress. Wait for it to finish, or stop it in the thread, then delete the job. Deleting a thread also deletes its job.

When Runs Fail ​

A run fails when it can't start, is stopped before it finishes, or ends waiting on an approval. The reason appears under Recent runs, and the collapsed card reads Last run failed.

After three failed runs in a row, the job stops. Its status changes to Stopped and the card says "Stopped after repeated failed runs. Resume it once the cause is fixed." Fix the cause, then click Resume. A successful run resets the count.

A job runs only while its owner is an active member with the Manager role or higher. If your account is deactivated or your role drops below Manager, its runs fail and the job stops after three of them.

Scheduled Jobs or Scheduled Runbooks? ​

Scheduled jobScheduled runbook
Set up byAsking in an Explore threadThe runbook's Schedule panel
CadenceAny pattern, at most once an hourWeekly or monthly
ScopeWhatever you can reach, including your personal connectionsThe companies chosen for the schedule
ApprovalsOnly tools you pre-approved run without asking; anything else is skippedThe runbook's approval settings. See Runbook Safety & Controls.
ResultsPosted in the job's threadThe execution summary in Executions & Monitoring
Good forPersonal digests, recurring checks, and reportsRepeatable processes your team relies on

Troubleshooting ​

  • "Scheduled jobs need the Manager role or higher" -- Ask an admin to check your role under Settings > User Management.
  • "You already have 10 scheduled jobs" -- Delete a job you no longer need, then ask again.
  • "A job can run at most once every 60 minutes" -- Choose a schedule with at least an hour between runs.
  • "This thread already has a scheduled job" -- Change the existing job, or start a new thread for another one.
  • "That schedule never occurs" -- The date can't happen, such as February 31. Check the day of the month and the month.
  • "Scheduled jobs are created from an Explore thread in the Junto web app" -- You asked from Slack or Teams. Open Explore in the web app instead.
  • A run says it skipped an action -- That action needs approval and isn't pre-approved for the job. Ask in the thread to pre-approve it, or do it yourself.
  • "This job is running" -- You tried to delete a job while a run is in progress. Wait for the run to finish, or stop it in the thread, then delete the job.
  • The job shows Stopped -- Three runs in a row failed. Check Recent runs for the reason, fix it, then click Resume.