🔎 Email - BY DESIGN

The following points are not considered issues:

• Single-edit only — the Mail Inbox > Folder field in Modalities Service Settings is shown in Bulk Editing mode, but is disabled. Each folder must be applied in single edit, as only one service can subscribe per folder.
• Folder renaming — Renamed Inbox folders are detected upon next sync. Nimbus will use the ID of the folder, not the name, so the name change will not cause interruptions.
• Mail or Folder selection changes will not retroactively generate tasks —   Nimbus is not using a polling subscription/change notifications functionality, meaning that Nimbus will process only those Emails, that appeared in Inbox folder only after the mailbox was (re)assigned to a service. While Nimbus is subscribed to the mailbox and monitoring its folders, incoming mails will be detected and generate tasks.

Handling interruptions

• If for any reason the subscription to an Exchange mailbox is interrupted, removed or suspended (as indicated in the Modalities Service Settings below the “Mailbox” pulldown), any mails received during this downtime will NOT be handled. 
  • In the same manner – when a mailbox is removed or otherwise re-applied the same service – it will treated the same as a newly subscribed mailbox. Existing mails will not be processed retroactively.
  • The same rule applies for a tenant resumed from suspension. Any mails that were received outside of a subscription period will not be processed retroactively.

🤔 Why is it handled like this?  This is by design. As the maximum tasks are limited by Tenant Settings it protects the Task Queue and Distribution from flooding with potentially stale and outdated tasks.

🤔 Which cases are handled? Any interruption to the Mailbox subscription caused on Nimbus side will result in Nimbus resuming the tasks where left of. 

🤔 What can I do to reprocess mails? While a service is subscribed to the folder (via Modalities Service Settings), move your mails out of, then back into a subscribed folder. However, note that this may generate a huge backlog of tasks, and Nimbus does not perform any duplication checks.