OdooWiki OCA HUB

Mail Notification - Clean up notifications in error

mail_notification_clean_status_error folder_open OCA/mail open_in_new
Mail License: AGPL-3

Delete email notifications in error.

The scheduled action Notification: Delete Notifications older than 6 Month provided by Odoo is responsible to delete notifications that have been sent successfully.

However, it doesn't delete the notifications that could not be sent, and their number could keep growing over time, impacting the performance of some queries related to the chatter.

This module extends the scheduled action of Odoo to also delete such notifications.

auto_awesome What this module does

AI-generated from the code · Odoo 18.0

Extends Odoo's automatic notification cleanup so that failed email notifications (bounced or in error) are also deleted, not just the successfully sent ones.

Odoo already runs a scheduled job that removes old email notifications from the chatter, but it only cleans up notifications that were sent successfully. Failed ones stay in the database forever and can slow down chatter-related queries.

This module hooks into that same cleanup routine on the mail.notification model. When the scheduled action runs, it now also looks for notifications that are marked as read, whose read date is older than the configured age (180 days by default), and whose delivery status is either "bounce" or "exception". Those records are then permanently deleted.

  • No new menu, screen or button is added; the change happens silently in the background.
  • The existing scheduled action "Notification: Delete Notifications older than 6 Month" is the one that triggers the cleanup.
  • The age threshold follows the same parameter as the standard cleanup, so it stays consistent.

In short, users get a cleaner and faster chatter over time without doing anything, because failed email notifications no longer pile up indefinitely.

Depends on

mail

Text generated by AI (DeepSeek) from reading the Odoo 18.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 2 confirmed, 7 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.