Jobs and notifications
Follow the work Halo runs in the background, retry or cancel a job, and choose which notifications also email you.
Long work, such as discovery or an export, runs in the background as a job. You can leave the page while it runs, and Halo tells you when it's done.
See your jobs
The Jobs button in the top bar shows Your jobs while they run, with progress. The Jobs page in the sidebar lists them in full.
On the page, filter by All, Running, Failed or Succeeded. If your role has See everyone's jobs, you see the organization's jobs, and Only mine narrows the list to yours. Otherwise you see your own.
Kinds of job
Discovery of a connection
File uploads: reading a file, then importing it
Extract refreshes
Data exports
PDFs of reports
Scheduled email of reports
Scheduled publishes, which wait in the list until their time
Snapshots behind public links and embeds
Image processing
Templates: saving one, and creating a report from one
Duplicating and importing reports
Generating or rebuilding a report with Halo, and Halo AI's descriptions and insights
Loading a dbt project
Writing a summary for a scheduled email
Publishing a website, and making a preview of one to share
Reading a directory source, and refreshing the directory's tables in Halo Data
Open a job
Press a job to see it in full.
Its progress, while it runs.
Details: when it was queued, started and finished, how long it took, and which attempt this is.
Log: what the job did, step by step.
What it made, such as an export, with when the file expires. An expired file says to export again.
A link to what it worked on, such as Open the connection, Open the dataset or Open the report.
If Halo restarts while a job is running, the job gets a little time to finish, then goes back in line and starts again from the beginning. That doesn't count as a failed attempt, and nobody's told it failed. Until it restarts, it says "Interrupted by a restart. It will start again."
Cancel or retry a job
Cancel job asks a queued or running job to stop. It says "Canceling…" until the job reaches a point where it can stop.
Retry job runs a failed or canceled job again. Use it once you've fixed what the error says, such as a connection's password.
Both are also in a job's right-click menu, along with Copy the error for a failed job.
Notifications
The bell in the top bar is the notification center. Everything Halo tells you appears there, and a dot on the bell means something's unread. Press a notification to go to what it's about. Mark all read clears them.
Long jobs that finish or fail tell you here, as do requests to publish, editions that don't build, changes that break a dataset of yours, data alerts, replies from Halo, website news such as a form response or a domain going live, what's new in your directory's Inbox, and plan limits if you're an Owner or an Admin.
Choose what emails you
Every notification appears in the notification center. In Account, under Notifications, choose which ones also email you. Your choices apply in every organization you belong to.
| Group | Email when | By default |
|---|---|---|
| Jobs | A long job fails: one you started, after running for more than 5 minutes | On |
| Jobs | A long job finishes: one you started, after running for more than 5 minutes | Off |
| Sharing | Someone shares something with you: a report, chart, dataset, folder or workspace, or more access to one | On |
| Reports | Someone asks you to publish: a request waits for your approval | Off |
| Reports | A summary needs your approval: Halo AI wrote a summary for a scheduled email to addresses outside your organization | Off |
| Reports | Your request is approved: an approver publishes a report you asked to publish | Off |
| Reports | Your request comes back: an approver sends it back with a note | Off |
| Reports | Your request is closed: someone publishes a newer version before it's decided | Off |
| Reports | Data changes under an edition of yours: someone changes a dataset's row policies or hidden fields, and couldn't withdraw the edition | Off |
| Reports | An address stops getting your report's email: it bounced for good, or its reader reported it as spam | On |
| Reports | An edition you published doesn't build: links still show the edition before it | Off |
| Data | A source change breaks a dataset: discovery finds a table or column gone that a dataset reads, yours or on a connection you administer | On |
| Data | Marketplace data has a new major version: a package you have changes fields, and you stay on your version until you move or its window ends | On |
| Data | dbt tests fail on a dataset of yours: a dbt test starts failing on a table it reads | Off |
| Data | Tables Halo keeps in Halo Data stop refreshing: Halo CRM's, Halo CMS's or Halo activity's tables that you look after, or the copy an overlay of yours joins on, with why, such as their connection going to the Trash or being deleted for good | On |
| Halo | Halo announces something: maintenance, incidents and news | Off |
| Halo | Halo answers your request: a reply to a request you sent from Contact Halo | On |
| Plan | Your organization nears a plan limit: at 80%, for Owners and Admins | Off |
| Plan | Your organization uses all of a plan limit: at 100%, for Owners and Admins | On |
| Data alerts | A data alert of yours fires: a number you follow crosses the line you set | On |
| Data alerts | A data alert of yours pauses, stops or starts again: what it follows went to the Trash or came back, changed, or you lost access to it | On |
| Websites | A website's address starts working: one you connected goes live | On |
| Websites | A website's address stops working: its DNS moved away, so readers stay on your Halo address | On |
| Websites | A website's numbers stop refreshing: on a website you made live, saying why, such as you can no longer read or publish them, a dataset behind them went to the Trash, or someone changed who may see what in it | On |
| Websites | A website's data source stops answering: a data source on a website you published doesn't answer | Off |
| Websites | A website's form gets a response, on a website you published | Off |
| Websites | A scheduled publish doesn't happen: a website you set to publish later couldn't go out | On |
| Halo CRM | Something arrives in Halo CRM's Inbox: a business asks to join or sends in a change, a source finds something, or a website's form sends a lead | Off |
| Halo CRM | Something Halo CRM reads keeps failing: a source failed three times in a row, or a website's form response couldn't reach the Inbox | On |
| Halo CRM | A task you were given is due: within a day | On |
| API keys | An API key is made as you: if it wasn't you, revoke it | Always |
| API keys | Your API key is about to end: within seven days | On |
| API keys | An Owner, an Admin or Halo revokes your API key | On |
Each switch says when it's been changed from its default. Halo emails important announcements itself, whatever your choice here. Some emails aren't optional: sign-in codes, password resets, invitations, and security warnings such as a two-factor lockout.
Scheduled report emails have their own recipients. See Scheduled email.