Skip to main content

How to Schedule Automated Tasks

Create scheduled rules that run actions at specific times — like sending device commands every morning or generating reports weekly.

Quick Summary

Click Smart Workflows in the sidebar, click Create Smart Workflow, select Time-Based trigger, set the schedule, add actions, and save.

Before You Begin​

Requirements
  • You need workflows:create permission
  • Target devices must be registered
  • Plan limits apply to number of scheduled rules

How Scheduled Rules Work​

⏰ Schedule triggers
       ↓
🔄 Infodeck executes at scheduled time
       ↓
⚡ Run configured actions
       ↓
📝 Log execution

Step-by-Step: Create a Time-Based Workflow​

Step 1: Open Smart Workflows​

  1. Click Smart Workflows in the sidebar
  2. Click Create Smart Workflow
  3. Select Time-Based trigger type

Step 2: Enter Workflow Details​

FieldRequiredDescription
NameYesWorkflow name (e.g., "Morning Sensor Check")
TagsNoTags for organizing workflows

Step 3: Configure Schedule​

Choose schedule type:

Cron-Based Schedule​

Run at specific times:

FieldOptionsExample
At Hours0-239 (9:00 AM)
At Minutes0-590 (on the hour)
Days of Month1-31, or empty for all[1, 15] (1st and 15th)

Rate-Based Schedule​

Run at regular intervals:

IntervalUse Case
Every 5 minutesHigh-frequency checks
Every hourRegular status updates
Every dayDaily reports

Step 4: Add Actions​

Click Add Action:

Action TypeDescription
Enqueue CommandSend command to IoT device
Send NotificationAlert users or teams
Generate ReportCreate scheduled report

Step 5: Save the Workflow​

Choose how to save your workflow:

ButtonDescription
Save as draftSave without activating — workflow won't run
CreateSave and activate — schedule becomes active immediately

Real-World Examples​

Example 1: Daily Sensor Wake-Up Command​

Situation: Battery-powered sensors sleep overnight to conserve power. You need them active by 6 AM when the facility opens.

Solution:

  1. Create Time-Based Workflow:
    • Name: Morning Sensor Activation
  2. Configure schedule:
    • At Hours: 6
    • At Minutes: 0
    • Days: All (empty = every day)
  3. Add action:
    • Type: Enqueue Command
    • Devices: All facility sensors
    • Command: Wake Up / Force Uplink
  4. Click Create to activate

Result: Every morning at 6 AM, all sensors receive wake-up commands and begin sending data before staff arrive.

Example 2: Weekly Energy Report​

Situation: Sustainability team needs a weekly summary of energy consumption for reporting.

Solution:

  1. Create Time-Based Workflow:
    • Name: Weekly Energy Summary
  2. Configure schedule:
    • At Hours: 8
    • At Minutes: 0
    • Days of Month: [1, 8, 15, 22, 29] (every Monday approximately)
  3. Add action:
    • Type: Send Notification
    • Recipients: Sustainability Team
    • Message: "Weekly energy report is ready"
  4. Click Create to activate

Result: Team receives notification every Monday morning to review energy data.

Example 3: Monthly Device Health Check​

Situation: IT needs to verify all IoT devices respond on the first of each month for compliance.

Solution:

  1. Create Time-Based Workflow:
    • Name: Monthly Device Health Check
  2. Configure schedule:
    • At Hours: 2 (2 AM to minimize disruption)
    • At Minutes: 0
    • Days of Month: [1] (first of month only)
  3. Add actions:
    • Action 1: Enqueue "Status Request" to all devices
    • Action 2: Notify IT Team "Monthly device check initiated"
  4. Click Create to activate

Result: On the 1st of each month at 2 AM, all devices receive status requests and IT is notified.

Example 4: End of Shift Sensor Interval Reduction​

Situation: Sensors report every 5 minutes during work hours but should switch to hourly reporting overnight to save bandwidth.

Solution:

  1. Create two scheduled rules:

Rule 1 - Evening Reduction:

  • Name: Evening - Reduce Reporting
  • Schedule: 18:00 (6 PM)
  • Action: Send "Set Interval 1hr" command

Rule 2 - Morning Restoration:

  • Name: Morning - Restore Reporting
  • Schedule: 06:00 (6 AM)
  • Action: Send "Set Interval 5min" command

Result: Sensors automatically switch between high-frequency (day) and low-frequency (night) reporting.

Schedule Configuration Reference​

Cron Fields​

FieldRangeExample
Hours0-239 = 9:00 AM
Minutes0-5930 = half past
Days of Month1-31[1] = 1st only

Common Schedule Patterns​

PatternConfiguration
Every day at 9 AMHours: 9, Minutes: 0, Days: (empty)
Weekdays at noonHours: 12, Minutes: 0, Days: (empty), with weekday filter
1st of month at midnightHours: 0, Minutes: 0, Days: [1]
Every 4 hoursRate: 4 hours

Action Configuration​

Enqueue Device Command​

FieldDescription
AssetTarget IoT device
Action NameCommand from Asset Type
fPortLoRaWAN frame port
PayloadHex command data
ConfirmedRequire acknowledgment

Send Notification​

FieldDescription
RecipientsUsers or teams
ChannelEmail, Push, or Both
MessageNotification content

Managing Time-Based Workflows​

View All Schedules​

  1. Click Smart Workflows in the sidebar
  2. Filter by type: Time-Based
  3. See all scheduled workflows with next run time

Edit Schedule​

  1. Click on the workflow row
  2. Modify schedule or actions
  3. Click Save
  4. Next execution uses new settings

Pause a Schedule​

  1. Find the workflow
  2. Toggle the status switch to disable
  3. Workflow won't run until re-enabled

Delete Schedule​

  1. Select the workflow checkbox
  2. Click Delete button
  3. Confirm deletion

Execution Monitoring​

View Execution History​

  1. Open the scheduled rule
  2. Navigate to History or Logs tab
  3. See past executions with:
    • Execution time
    • Success/failure status
    • Actions performed
    • Error messages (if any)

Common Execution Statuses​

StatusMeaning
SuccessAll actions completed
PartialSome actions failed
FailedExecution error
SkippedRule was disabled

Troubleshooting​

Schedule Not Running​

IssueCauseSolution
Workflow disabledStatus is Draft or offActivate the workflow
Wrong time zoneServer time mismatchVerify time settings
Past scheduleOne-time schedule passedUpdate schedule

Actions Not Executing​

IssueCauseSolution
Device offlineCan't receive commandsCheck device status
Invalid commandWrong payloadVerify command config
Permission errorInsufficient accessCheck workflow permissions

Missed Executions​

IssueCauseSolution
System maintenanceScheduled during downtimeAdjust schedule time
Rate limitingToo many rules at same timeStagger execution times

Best Practices​

Scheduling Tips​

PracticeBenefit
Stagger rule timesAvoid system overload
Use off-peak hours for bulk operationsReduce impact
Test with disabled status firstValidate before going live
Add buffer time for dependent actionsEnsure sequence completes

Naming Conventions​

GoodAvoid
Daily 6AM - Sensor Wake UpSchedule 1
Weekly Monday - Energy ReportReport rule
Monthly 1st - Device CheckCheck

Plan Limits​

PlanTime-Based Workflows
Lite❌ Not available
Basic5
Professional20
EnterpriseUnlimited
Plan Requirement

Time-based trigger workflows require Basic plan or above.

Need help? Contact Infodeck Support

Was this page helpful?