Wednesday 1 May 2024

What parameters are used in configuring a scheduler in MuleSoft?349

What parameters are used in configuring a scheduler in MuleSoft?

In MuleSoft 4, schedulers provide a mechanism to trigger the execution of your integration flows at specific intervals or based on defined schedules. Here are the key parameters you can use to configure a scheduler:

1. Scheduling Strategy:

This parameter defines how the scheduler determines when to trigger the flow execution. It has two main options:

  • fixed-frequency: Used for regular intervals. It requires a frequency attribute specifying the time unit (milliseconds, seconds, minutes, hours, days) and the interval value (e.g., frequency="1m" for every minute).

  • cron: Used for more complex scheduling patterns based on cron expressions. It requires a cron attribute where you define the schedule expression following the standard cron syntax (e.g., cron="0 0 12 * * ?" for every day at noon).

2. Frequency (Optional - Applicable for fixed-frequency strategy):

This parameter specifies the interval between flow executions when using the fixed-frequency strategy. You can define it in various time units like milliseconds (ms), seconds (s), minutes (m), hours (h), and days (d).

3. Time Unit (Optional - Applicable for fixed-frequency strategy):

This parameter defines the unit of time for the frequency value. Supported units include milliseconds (ms), seconds (s), minutes (m), hours (h), and days (d).

4. Delay (Optional):

This parameter specifies an initial delay before the first execution of the flow. It uses the same time unit as the frequency and allows you to postpone the first execution for a specific duration.

5. Correlation ID (Optional):

This optional parameter allows you to assign a unique identifier to each scheduled flow execution. This can be helpful for tracking and debugging purposes, especially when dealing with multiple scheduled executions.

6. Cron Expression (Optional - Applicable for cron strategy):

This parameter defines the schedule pattern using a cron expression format when using the cron strategy. Refer to cron documentation for details on defining specific scheduling patterns (

Here's an example configuration demonstrating both fixed-frequency and cron scheduling:


<flow name="ScheduledFlow">
    <fixed-frequency frequency="1m"/> </scheduler>
  <scheduler name="HourlyJob" cron="0 0 * * * ?"> <flow-ref name="HourlyProcessingFlow"/>

Remember, these are the core parameters for configuring schedulers in MuleSoft 4. Additional configuration options might be available depending on the specific scheduler implementation you're using (e.g., custom schedulers). Always refer to the MuleSoft documentation for the latest and most accurate information.




No comments:

Post a Comment

Note: only a member of this blog may post a comment.