Scheduler
You can trigger Nected rules and workflow via API and schedule them 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.
How to schedule a rule?
Nected allows you to schedule rules to run automatically based on a defined time interval. This capability is essential when rules need to be executed repeatedly—for example, to process new data entries, apply decisions periodically, or trigger external systems at scheduled times.
Important: Scheduler Requires a Database The scheduler only works for rules that use a connected database. It runs as a cron job over database rows. If your rule doesn’t use a dataset, scheduling won’t work. Edit or connect a data source →
Steps to Create a Schedule
Open the Rule
Navigate to the specific rule you want to schedule.
Access the Settings Tab
On the right-hand sidebar, open the Settings tab.
If the Settings tab is not visible, click on the gear icon located at the top-right of the rule editor.
Locate the Schedule Section
Within the Settings tab, scroll down to find the "Schedule" section.
Click 'Create Schedule'
Click the “Create Schedule” button to initiate the scheduling configuration.
Define Active Time Window
Provide the Start and End dates to define the active period during which the rule should execute.
The rule will only be triggered during this timespan.
Configure the Schedule Frequency: Set the frequency with which the rule should run. Read more about it in the next section.
After these steps, click on the “Create Schedule” button, and the rule will be scheduled. But as said earlier, it will only become operational when it is published. For post-scheduling actions, you can refer to the section “Editing & Updating the Schedules” .
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:
Minutes: Set the rule to execute at specified intervals in minutes. This is suitable for tasks that require frequent checks or updates.
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.
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.
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.
Monthly: Schedule the rule to run on selected days each month. This is ideal for monthly routines or checks.
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:
Minute (0 - 59): Specifies the minute of the hour for the task to run.
Hour (0 - 23): Indicates the hour of the day on a 24-hour clock.
Day of the Month (1 - 31): Determines the day of the month the task should execute.
Month (1 - 12): Defines the month during which the task runs.
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.
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.
How to Test the Scheduler?
Before enabling a schedule in production, it's essential to test the rule’s schedule configuration to confirm it behaves as expected. Testing helps validate that the rule processes data correctly based on your logic, frequency, and inputs. This controlled test environment allows for fine-tuning before live execution.
The Scheduler's built-in test mode simulates scheduled execution without impacting your production data or environment. You can verify how the rule runs over a subset of data, inspect outputs, and make logic adjustments accordingly.
Steps to Test the Scheduler:
Use the Test Schedule Feature
Open the rule and go to the Settings tab on the right-hand side.
Locate the “Test Schedule” button (visible where the production “Create Schedule” button is located).
Click Test Schedule to initiate a test run.
Provide Test Input Values
Fill in the input parameters your rule expects. These can be IDs, flags, or any required identifiers (e.g.,
Loan_amount,cusid).Click Test to trigger the rule with those inputs.
Review Execution Results
The system will return execution metrics: how many rows were processed, how many passed, and how many failed.
Use this feedback to validate logic and optimize configuration if needed.
Limits of Scheduling a rule:
Row Limit: In test mode, the scheduler processes data in 2 batches of 5 rows a total of 10 rows, running them in parallel.
Data Source Dependency: If the rule depends on a connected database, the Scheduler will automatically fetch relevant entries. Make sure database connectivity is active and inputs are valid.
Cron Scheduling: Custom cron expressions are not supported in test mode. The scheduler simply picks the first 10 entries and runs your rule logic over them once, without simulating timing-based recurrence.
Testing the scheduler before production deployment is a necessary step. It protects against logic errors, misconfigurations, and incomplete integration with data sources.
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.
How to Schedule a Workflow in Nected?
Unlike rules, workflows in Nected cannot be scheduled directly. To schedule a workflow, users must configure a rule that triggers the workflow via API or Webhook. The Scheduler is then applied to this rule, effectively scheduling the workflow indirectly. Follow this step-by-step procedure to schedule workflows:
Before starting, first, open the workflow and publish the workflow to make it available for external invocation.
Generate the Workflow API Endpoint
To schedule a workflow, you'll need to trigger it via API. For this:
Open the published workflow.
From the right-hand panel, go to Triggers.
Select Trigger via API or Trigger via Webhook, based on your requirement.
Copy the endpoint URL generated for the workflow.
For more details, refer to the documentation on Trigger Workflow via API and Trigger Workflow via Webhook.
Schedule the Rule
Once the rule is verified to trigger the workflow, schedule it as usual:
Switch to Production environment.
Click on Create Schedule from the Scheduler panel.
Choose the frequency: Minutes, Hours, Daily, Weekly, Monthly, or Cron.
Configure any required inputs.
Click Create Schedule.
Why You Should Schedule Your Workflow?
Scheduling workflows isn't just about convenience—it's about automating time-critical operations reliably. Here are three real-world scenarios that benefit from scheduled workflow execution:
Automated Daily Reconciliation Between Systems: If you're syncing data between two systems, such as a CRM and a billing platform, a scheduled workflow ensures that data remains consistent. Every night at 1 AM, a workflow could pull new customer entries, reconcile unpaid invoices, and push updates to the connected tools without any manual intervention.
Periodic Lead Scoring and Re-segmentation: Lead behavior changes frequently. By scheduling a workflow to run every few hours, you can dynamically reassess lead scores based on their actions (like email opens or site visits) and push updated segments to your marketing tools. This enables real-time personalization at scale.
Automated Report Generation and Dispatch: Internal and client-facing reports often need to be delivered on a schedule—daily, weekly, or monthly. A scheduled workflow can fetch data from your database, run aggregations, generate reports, and send them to predefined recipients via email or third-party APIs.
Although there are more use cases, here are these 3 of them that demonstrate how scheduled workflows can streamline operations, improve accuracy, and free up your team from repetitive tasks.
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. Follow this steps to monitor the schedulers:
Go to the Audit Trail Page:
Go 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.
Interpreting Audit Log Entries:
The Audit Log displays a chronological record of scheduler events, 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.
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