How to Configure Scheduled Actions in Odoo 19

Modern business operations thrive on efficiency, largely achieved through the automation of repetitive, time-sensitive tasks. In Odoo 19, this essential automation capability is delivered by Scheduled Actions, often referred to as Cron Jobs. These actions are designed to execute predefined operations seamlessly in the background, requiring no manual intervention. This robust functionality is crucial for maintaining data consistency, generating periodic reports, dispatching timely notifications, and supporting a wide array of other critical business processes.

This comprehensive guide will lead you through the fundamental concepts and practical implementation of scheduled actions in Odoo 19, providing a clear and actionable framework for effectively automating your business operations.

The Scheduled Actions Menu

Odoo furnishes a centralized and intuitive interface for managing all automated tasks, offering a comprehensive overview and control point. You can easily access this powerful feature by navigating to:

Settings > Technical > Scheduled Actions

This dedicated menu presents a clear list view of all existing cron jobs, displaying vital information at a glance. Key details include:

• Action Name: A descriptive label that identifies the purpose of the automated task.
• Model: Specifies the particular Odoo model (e.g., res.partner for contacts) on which the scheduled action will operate.
• Next Run: Indicates the precise date and time when the system is scheduled to execute the task next.
• Interval: Defines the frequency at which the task recurs (e.g., every 5 minutes, once a day, weekly).
• Active: A simple toggle switch to enable or disable the scheduled task as needed, allowing for flexible management.

From this central management interface, users can effortlessly create new scheduled actions. By clicking the "New" button, a configuration form appears, allowing for the meticulous setup of all necessary parameters, including the specific Python code to be executed for the task.

Defining Cron Jobs via XML

While Odoo's user interface offers a convenient way to manage scheduled actions, developers often prefer defining them within a module's code for enhanced maintainability, version control, and seamless deployment alongside custom features. This approach integrates automation directly into your development workflow.

To implement this, you typically create an XML file, often named data/ir_cron_data.xml, within your custom module. This file contains the structured definition of your cron job. Below is a detailed example of a common cron job definition:

<?xml version="1.0" encoding="UTF-8"?>
<odoo>
    <data noupdate="1">
        <record id="cron_send_daily_reminder" model="ir.cron">
            <field name="name">Daily Customer Follow-up</field>
            <field name="model_id" ref="model_res_partner"/>
            <field name="state">code</field>
            <field name="code">model._send_daily_followup()</field>
            <field name="user_id" ref="base.user_root"/>
            <field name="interval_number">1</field>
            <field name="interval_type">days</field>
            <field name="nextcall" eval="(DateTime.now() + timedelta(days=1)).strftime('%Y-%m-%d 09:00:00')" />
            <field name="priority">5</field>
            <field name="active">True</field>
        </record>
    </data>
</odoo>

Let's thoroughly deconstruct the essential attributes within this XML definition:

• <data noupdate="1">: This is a critical wrapper tag. The noupdate="1" attribute ensures that this record is created only once when your module is initially installed. Crucially, subsequent updates to your module will not overwrite any modifications made to this cron job directly within the Odoo database, thus preserving its state and user-specific adjustments.
• id & model: The id attribute provides a unique, module-specific identifier for this particular record (e.g., cron_send_daily_reminder). The model="ir.cron" attribute explicitly tells Odoo that we are defining a Scheduled Action, as ir.cron is the designated model for managing these tasks.
• name: This field holds a clear, human-readable label for the scheduled action. This name is prominently displayed in the Odoo technical menu, making it easy to identify the purpose of the task.
• model_id: This attribute references the specific Odoo model that the scheduled action will interact with or operate upon. The ref attribute uses the model's external or technical ID (e.g., model_res_partner for the Partner model) to establish the link.
• state & code: These two attributes work in conjunction to define the action's core logic. state="code" instructs Odoo that the action involves executing custom Python code. The code attribute then contains the actual Python method call, such as model._send_daily_followup(). In this context, model represents an instance of the target Odoo model, and _send_daily_followup() is the custom Python method designed to perform the desired automated task.
• user_id: This field specifies the user context under which the Python code of the scheduled action will be executed. It's common practice to use ref="base.user_root" (referencing the superuser) to circumvent potential permission-related issues and ensure the task has sufficient privileges to perform its operations.
• interval_number & interval_type: These attributes meticulously define the frequency of the scheduled execution. interval_number takes an integer value (e.g., 1), while interval_type specifies the unit of time, which can be minutes, hours, days, weeks, or months, allowing for flexible scheduling.
• nextcall: This attribute sets the precise timestamp for the initial execution of the scheduled action. The eval attribute is particularly powerful, enabling dynamic calculation using Python expressions. The example demonstrates scheduling the first run for 9:00 AM on the day following the module's installation or update.
• priority: A numerical value that determines the execution order within the queue when multiple scheduled jobs are due to run at the same time. A lower number indicates a higher priority, meaning that action will be executed before others with higher priority numbers.
• active: A boolean field (True or False) that controls whether the scheduled action is currently enabled and will run according to its schedule. Setting it to True activates the cron job.

Implementing the Business Logic: The Python Method

The XML definition of a scheduled action merely points to a specific method; the actual business logic resides within a Python method defined in the relevant Odoo model file. This method encapsulates the core operations of your automated task.

from odoo import models, fields, api

class ResPartner(models.Model):
    _inherit = 'res.partner'

    def _send_daily_followup(self):
        """
        Automated method to send a follow-up email to partners.
        This method is designed to be called by a scheduled action (cron job).
        """
        # Example: Fetch all partners who are classified as customers
        # The search method allows filtering records based on specified criteria.
        customer_records = self.search([('customer_rank', '>', 0)])

        # Retrieve a predefined email template from the system
        # 'my_module.email_template_daily_followup' refers to an XML ID of an email template
        mail_template = self.env.ref('my_module.email_template_daily_followup')

        # Iterate through each identified customer and send the personalized email template
        for partner in customer_records:
            # send_mail queues the email for sending, force_send=False ensures it's added to the mail queue
            # rather than sending immediately, which is ideal for bulk operations.
            mail_template.send_mail(partner.id, force_send=False)

Scheduled Actions are a fundamental pillar of automation within Odoo 19, effectively transforming manual and often repetitive tasks into reliable, background processes. By strategically utilizing the ir.cron model, through either Odoo's intuitive user interface or precise code-based definitions in XML, developers can construct sophisticated automation workflows for a diverse range of operational requirements. This includes:

• Automating the dispatch of scheduled emails, reminders, and essential notifications to customers or internal teams.
• Performing routine nightly data clean-up operations, archiving old records, or executing batch updates to ensure data integrity and system performance.
• Generating and distributing daily, weekly, or monthly reports automatically, providing timely insights without manual effort.
• Dynamically updating calculated fields, statuses, or other record attributes based on elapsed time or specific conditions, ensuring data accuracy and relevance.

A firm grasp of this feature empowers businesses to forge a more streamlined, efficient, and virtually error-free operational environment. By automating critical tasks, organizations can ensure that important processes are never overlooked, allowing employees to dedicate their valuable time and expertise to higher-value, strategic initiatives that drive growth and innovation.