Discuss automations

Discuss runs eight scheduled jobs, and has no automation rule and no e-mail template. All eight are installed active except the incoming mail job; a test or restored copy of the database has them off. An administrator stops one by deactivating its scheduled action among the scheduled actions of the technical menu, in developer mode. The options of Discuss are listed in Discuss settings.

Discuss

End of a mute

• When: once a day, and at the exact time a mute ends (Discuss: channel member unmute).
• What it does: clears the mutes whose time is up, so that a muted channel calls for your attention again. See Choose your notifications and mute a channel.
• How to stop it: deactivate the scheduled action; muted channels then stay muted until unmuted by hand.

Browser notifications

• When: right after a message that must notify someone, and once a day as a backstop (Mail: send web push notification).
• What it does: sends the waiting notifications to the browsers of the users who clicked Enable under Turn on notifications, in batches of fifty. Nothing is sent while the server has no push keys.
• How to stop it: deactivate the scheduled action, or refuse notifications in the browser.

Messages sent later

Delayed notifications

• When: every hour, and at the time a delayed notification is due (Notification: Notify scheduled messages).
• What it does: sends the notifications of messages that were posted with a later sending date, once that date has come.
• How to stop it: deactivate the scheduled action; such notifications then wait until it runs again.

Scheduled messages

• When: once a day, and at the time chosen for each scheduled message (Mail: Post scheduled messages).
• What it does: posts the messages written in the chatter of a record to be sent at a later time, fifty at a time. The chatter is explained in Follow a record with the chatter.
• How to stop it: deactivate the scheduled action; the messages then stay scheduled and are not posted.

E-mail

Outgoing e-mail queue

• When: every hour (Mail: Email Queue Manager).
• What it does: sends the e-mails waiting in the queue, up to a thousand at a time, such as the notifications of users who chose By Emails.
• How to stop it: deactivate the scheduled action; e-mails then wait in the queue. Mail servers are explained in Email: outgoing and incoming servers.

Incoming mail

• When: every five minutes, and only while an incoming mail server is active (Mail: Fetchmail Service). It is installed inactive and turns itself on with the first active incoming server.
• What it does: fetches the e-mails of the incoming servers and turns them into messages or records.
• How to stop it: deactivate the incoming mail servers, or the scheduled action.

Housekeeping

Old notifications

• When: once a month (Notification: Delete Notifications older than 6 Months).
• What it does: deletes the notifications of internal users that were read more than 180 days ago and were delivered or cancelled. The messages themselves stay.
• How to stop it: deactivate the scheduled action; the notifications are then kept.

Weekly technical check

• When: once a week (Publisher: Update Notification). The list of scheduled actions does not show it.
• What it does: a technical check with the publisher of the platform. Jaah blocks it, so nothing leaves the server.
• How to stop it: nothing to do; it is already blocked.