Scheduler

Along with Triggering Nected rules and workflow via API, you can also schedule rules and workflow to run at periodic intervals.

Imagine segmenting customers automatically, syncing data across databases, or setting dynamic discounts based on time, all scheduled precisely. Similarly, daily reports, anomaly alerts, and much more, all happening automatically on your schedule.

With Nected Rule connected with database, it can run rule over database entries and can take up respective rule action for matching rows, While if Nected Rule is configured with external API as source in input attributes, it will be trigger the external API and can take any action based on value or changes in the response.

This documentation provides a comprehensive guide on how to effectively utilize the Nected Scheduler. It covers the setup process, usage in both test and production environments, managing and monitoring schedules, and addresses limitations and upgrade paths.

Getting Started with Nected Scheduler

To begin using the Nected Scheduler, users must first engage with the rule creation process within the Nected platform. Access to the scheduler is directly tied to the rules that users set up. Here are the specific steps to access the Scheduler feature:

  1. Rule Creation or Selection:

    • If you are a new user or have not yet created any rules, your first step is to create a rule within the Nected platform. This process involves defining the parameters and conditions of the rule as per your workflow requirements.

    • For users who have pre-existing rules, you can simply select one of your already created rules. This is done by navigating to the list of your rules and clicking on the desired rule to open its details.

  2. Navigating to the Scheduler:

    • Once a rule is created or selected, you will be directed to the rule window. Here, you will find various options and settings related to the rule.

    • To access the Scheduler, look for the Scheduler button. This button is located on the right side of the rule window.

    • Clicking on the Scheduler button will take you to the Scheduler interface. This is where you can set up and manage the scheduling of your rule.

There are no additional prerequisites or special requirements to access the Scheduler feature. It is readily available once a rule is created or selected. This straightforward access ensures that all users, regardless of their technical expertise, can easily schedule and automate their rules on the Nected platform.

Using the Scheduler in Staging

Test Mode, also known as the Staging environment in the Nected Scheduler, is a critical feature for validating and fine-tuning rules before their deployment in a live setting.

Test Mode in the Nected Scheduler, functioning within the Staging environment, is essential for trialing and refining rules using sample values before their deployment in a live setting. This mode facilitates the execution of rules on a limited data set, enabling users to verify their functionality and effectiveness.

Steps to Use Scheduler in Staging:

  1. Accessing Test Scheduler:

    Within the Staging environment, locate and select the 'Test Schedule' option. This is typically found on the right side of the screen when in the staging phase, leading you to the test scheduling interface.

  2. Configuring Test Schedule:

    • Upon entering the test scheduling interface, users are presented with the 'Test Cron' ’Test Schedule**’** window. This window is where you set up the schedule for testing your rule.

    • Here, you will input various attributes relevant to your rule. These 'input attributes' might include parameters like the number of tests to run, specific identifiers, or other relevant data points. It's important to note that these attributes will vary based on the rule and its requirements.

  3. Executing the Test Scheduler:

    • After configuring the input attributes, initiate the test by clicking the 'Test' button.

    • In Test Mode, the Scheduler executes the rule for only the first 10 rows of your data set. This limitation is purposefully designed to streamline the testing process.

    • The output section will display the results of the test, showing the execution details for the specified rows.

Limitations

  • Row Limit: The Scheduler in Test Mode processes only the first 10 rows of your data set. This constraint is essential for efficient testing and resource management.

  • Data Handling: Depending on your rule, the Scheduler may automatically fetch certain data from your connected database. Ensure that your database connections are correctly set up for accurate test results.

πŸ’‘ Keep in mind the limitations in the Production environment, such as the Cron job Scheduler's cap. If your needs exceed these limits, consider upgrading your plan for expanded scheduling capabilities.

Utilizing the Scheduler in Test Mode is a vital step towards ensuring the reliability and accuracy of your rules in the Nected platform. This mode offers a controlled environment for testing, giving users the confidence and assurance needed before proceeding to a production environment.

Transitioning to Production

After successfully testing rules in the Staging environment, the next step is to transition them to Production. This phase involves setting up the scheduler for actual data sets and operational environments, ensuring that the rules are executed as intended in real-world scenarios.

Steps for Setting Up Scheduler in Production

  1. Switching to Production Mode:

    To begin, switch from the Staging environment to the Production environment. This is typically done by selecting the 'Production' tab within the Nected platform.

  2. Creating a Production Schedule:

    In the Production environment, you will find options to create a new schedule for your rule. This involves specifying the start and end dates for the rule execution, defining the time frame within which the rule should operate.

  3. Configuring Schedule Frequency:

    The Nected Scheduler offers various options for scheduling frequency, allowing users to tailor the execution of their rules according to specific needs. These include:

    1. Minutes: Set the rule to execute at specified intervals in minutes. This is suitable for tasks that require frequent checks or updates.

    2. Hours: Schedule the rule for execution on an hourly basis. This option is ideal for daily routines that need to run several times throughout the day.

    3. Daily: Choose a specific time for the rule to run each day. This setting is useful for daily tasks that need to occur at the same time every day.

    4. Weekly: Select specific days of the week for the rule to execute. This option is beneficial for tasks that are required on certain days each week.

    5. Monthly: Schedule the rule to run on selected days each month. This is ideal for monthly routines or checks.

    6. Cron: For more complex scheduling needs, the Cron option allows users to define custom schedules using Cron expressions. This advanced feature provides flexibility for intricate scheduling requirements.

      Cron: The Cron scheduling option in Nected is designed for complex scheduling needs. It allows users to define custom schedules using Cron expressions, a powerful and flexible way to specify time and frequency for tasks. Cron expressions are strings of text composed of five fields, representing a time schedule in the following format:

      1. Minute (0 - 59): Specifies the minute of the hour for the task to run.

      2. Hour (0 - 23): Indicates the hour of the day on a 24-hour clock.

      3. Day of the Month (1 - 31): Determines the day of the month the task should execute.

      4. Month (1 - 12): Defines the month during which the task runs.

      5. Day of the Week (0 - 6): Represents the day of the week, where 0 stands for Sunday, 1 for Monday, and so on.

      Each field can contain specific values, ranges, and special characters like '*' (representing all possible values) and '/' (indicating increments). For instance, a Cron expression '0 12 * * 1' means the task will run at 12:00 PM every Monday.

      This advanced feature caters to intricate scheduling requirements, offering users the ability to precisely control when their rules are executed.

  4. Finalizing the Schedule:

    • After choosing the schedule type and setting the parameters, finalize the schedule by clicking the 'Create Schedule' button.

    • You may also need to input test values, i.e. specific identifiers, depending on your rule configuration.

Editing and Updating Schedules

Once a schedule is created, it can be edited or updated at any time. This is done by selecting the 'Edit Schedule' option, allowing for adjustments in response to changing requirements or conditions.

Limitations:

Cron Limit: In the Production environment, there is a default limit of 500 Cron jobs. If your scheduling needs exceed this limit, an upgrade to a higher plan is necessary.

πŸ’‘ Keep in mind the limitations in the Production environment, such as the Cron job cap. If your needs exceed these limits, consider upgrading your plan for expanded scheduling capabilities.

Monitoring Schedulers

Effective management and monitoring of schedulers are essential for ensuring their optimal performance in the Nected platform. This section guides you through the tools and methods for overseeing and adjusting your schedulers.

For detailed information on what the Audit Trail is and how it functions, refer to the Nected Audit Trail documentation.

Using the Audit Trail for Monitoring

  1. Accessing the Audit Trail:

    Navigate to the 'Audit Trail' or 'Audit Log' screen within the Nected platform to monitor scheduler activities. This feature provides a comprehensive log of all actions and changes.

  2. Interpreting Audit Log Entries:

    The Audit Log displays a chronological record of events related to schedulers, including updates and test executions. Each entry details the action taken, the rule involved, and the outcome, allowing for effective tracking and analysis of scheduler performance.

  3. Verifying Scheduler Execution:

    Audit Logs are crucial for confirming the execution of schedulers, showing detailed information about each run. For instance, if a scheduler is set for a 10-row test execution, the log will confirm this, providing transparency and assurance of the scheduler's functionality.

Regular management and monitoring of your schedulers in Nected, facilitated by the Audit Trail and user-friendly management tools, are key to maintaining efficient and reliable automated workflows. Regular reviews of the Audit Logs and updates to scheduler settings ensure that your automated processes remain aligned with your operational needs.

Conclusion

The Nected Scheduler is an essential tool for enhancing workflow efficiency in the Nected platform. It's crucial to utilize the Test Mode for rule validation and regularly monitor the Audit Trail for optimal scheduler performance. Be mindful of the limitations in both Test and Production modes, and consider upgrading your plan as needed. Embracing these practices will ensure smooth and effective operations, maximizing the benefits of the Nected Scheduler.

Last updated