Appearance
Jobs
The Jobs page lets an admin start a background job now instead of waiting for its schedule. Reach for it after you change something: run the documentation sync once you have fixed a page, or the conversation sync once a new help desk is connected, and the knowledge base catches up straight away.
What's on the page
Jobs are grouped by what they work on:
- Triage: Auto-triage.
- Agent: Auto-draft replies, Follow-up nudges, Close stale conversations and Score drafts against replies.
- Knowledge base: the syncs your workspace has, one for each source you have connected.
Everyone on your team can read the page. Each card says how the job runs. "Automatic" shows its frequency and next run time, Automation paused means its schedule is switched off, and Manual only means it has no schedule and runs only when someone starts it.
Reports and analyses are started from their own pages, with Generate report on Reports and Run analysis on Analyses. Agents can start those; running a job from Jobs is for admins.
A new workspace's sync cards appear a minute or two after setup, once Overdesk has created their schedules.
Run a job now
- Open Jobs in the sidebar.
- Find the job and click Run now.
- A message confirms it started. If the job is already running, Overdesk tells you so and doesn't start a second copy.
- Follow its progress on Runs.
Only admins and the owner can start jobs. For agents and viewers the page shows the jobs without a Run now button.
A manual run follows the same rules
Pressing Run now starts the same job the schedule starts, with the same settings and the same limits:
- Auto-draft replies still needs a documentation source, works only in the inboxes your Allowed inboxes setting allows, and leaves every draft unsent for a person on your team, except the replies your guardrails approve on a workspace that has turned sending on.
- Close stale conversations closes real conversations in your help desk, and only in inboxes you have named in Allowed inboxes. Read Closing stale conversations before you run it.
- A sync whose integration isn't connected refuses to start and tells you what to connect first.
Pausing a schedule doesn't stop you running the job by hand. The card shows Automation paused, and Run now still works.