Overview
Altera can email you when an import or export job starts, completes, or has an error. You set the defaults once for your store, then override them on individual jobs when a job needs different recipients or no emails at all.
This article covers:
Store-level notification settings that apply to every job
Per-job settings that override the store settings for one job
Common questions about notification emails
Store-level notification settings
Store-level settings are the defaults for every job on your store, including scheduled jobs.
In Altera, click Settings > General.
In the Notifications card, select the events you want to be emailed about: A job starts, A job completes, or A job has an error.
In Send the notifications to, enter one or more email addresses. Separate multiple addresses with commas.
Click Save.
If no events are selected, or the recipient list is blank, Altera sends no job emails.
Per-job notification settings
A single job can use different settings from the rest of the store. For example, an export that runs every hour does not need to email the whole team, and a one-time migration might need to notify a client.
Open the job from the Jobs list.
Click More actions > Notifications. The Email notifications dialog opens.
Choose one of the options below and click Save.
Use store settings
The default. The job follows the store-level settings, and any later change to the store settings also applies to this job.
Custom for this job
The job uses its own settings:
Select which events send an email: A job starts, A job completes, or A job has an error.
In Recipients, enter the email addresses for this job, separated by commas. This list replaces the store recipients. Leave it blank to keep the store recipients but change only the events.
When you first switch to Custom for this job, the events are pre-filled from the store settings. Recipients is pre-filled with the last custom list you saved on this store in this browser, or with the store recipients if you have not saved one yet, so you only need to change what is different.
Muted
The job sends no notification emails, regardless of the store settings.
How per-job settings behave
The settings apply to every future run of the job, so a muted scheduled export stays muted.
Altera checks the settings at the moment each email is sent. If you change them while a job is running, the change applies to that run.
When a job has custom or muted settings, a row at the bottom of the status card on the job page summarizes them, for example "Emails [email protected] when: a job completes, a job has an error" or "Notifications are muted for this job". Click Change to open the settings.
Store settings are never changed by a per-job override.
Common questions
I did not get an email for a job
Check the following, in order:
Open the job and look for a notifications row at the bottom of the status card. If it says the job is muted, that is why.
If the row shows custom settings, check that the event and recipients match what you expect. Click Change to edit them.
If there is no row, check Settings > General > Notifications. The event must be selected and the recipient list must not be blank.
Check your spam folder. Notification emails come from getaltera.com.
How do I stop emails from a recurring export?
Open the job, click More actions > Notifications, choose Muted, and click Save. Other jobs keep using the store settings.
How do I send emails for one job to someone else?
Choose Custom for this job, replace the Recipients list with the new address, and click Save. To keep the store recipients and add someone, keep the store addresses in the list and add the new address at the end. Altera remembers the list you saved and offers it the next time you set custom notifications on a job in this store.
Do per-job settings affect the API or CLI?
Jobs created through the API, the CLI, or an MCP connection use the store settings unless you change them on the job page.