Wiresk

Wiresk

Wiresk Scheduler – The Fundamentals

Estimated reading time: 2 min
Wiresk's scheduler banner

Understanding Scheduled Triggers, Recurrence Rules, Jobs, and Execution Behavior

The Scheduler is a fundamental component of Wiresk. It lets you specify exactly when and how frequently a Flow should run, removing the need for manual starts. Scheduling applies to Triggers.

When you set a scheduler on a Flow, Wiresk does more than just “run it on time.” Here’s what happens:

Step-by-Step Execution Logic:

  1. Data Retrieval: At the scheduled time, Wiresk sends a request to the connected app (e.g., Odoo, Notion, HubSpot) to pull data based on your defined conditions (e.g., all contacts named “John”).
  2. Job Creation: Each data item retrieved becomes an individual job. For example, if 10 matching items are found, Wiresk creates 10 jobs.
  3. Flow Execution Per Job: Each job is passed through the Flow independently, meaning your Flow runs once per data item.

Wiresk uses a dual strategy for data processing to balance performance and reliability.:

  • Batch Retrieval: Wiresk pulls data in medium-sized batches (e.g., 100–1000 items at a time) to balance performance and resource efficiency.
  • Individual Processing: Despite batch retrieval, each data item is processed individually. This design ensures that if one item encounters an error during processing, it does not affect the processing of other items.
This strategy aligns with the behavior of many APIs, which often handle requests individually rather than in large batches. By processing items separately, Wiresk ensures compatibility with various APIs and reduces the risk of large-scale job failures due to a single erroneous data item.

When building a Flow, Wiresk provides a “Use” (formerly “Get Sample”) feature that pulls a sample item. You map fields based on this, and Wiresk reuses the mapping across all future jobs in that Flow.

Wiresk allows scheduling in two ways through the Recurrence Rule settings:

Use this to schedule a one-time execution.

  • Ideal for:
    • Initial data syncs
    • Setup tasks
    • Manual test executions
  • After execution, the schedule automatically clears.

Used to set repeating schedules across various timeframes.

These control how long the schedule stays active:

  • Repeat Forever
    • Keeps running without an end date.
    • Suitable for ongoing processes (e.g., checking every 10 minutes for new records).
  • Repeat for (x) Times
    • Runs a fixed number of times.
    • You must define the number in Number (x) of Repeat Times.
  • Repeat Between Start & End Dates
    • Runs within a specific timeframe.
    • You define the start and end dates.
    • Useful for campaigns, limited offers, or short-term automations.

You can select from the following recurrence frequencies:

ModeDescription
Daily at Multiple TimesRuns multiple times per day at intervals (e.g., every 15 mins).
DailyRuns once per day at a specific time (e.g., 15:13), with a repeat count.
WeeklyRuns on specific days of the week (e.g., Mondays at 10:00).
MonthlyRuns on a specific day each month.
YearlyRuns x times per year on a specific date and time.
Specified DatesRuns on user-selected dates and times.
  • Use Repeat (x) Times when testing Flows to avoid infinite executions.
  • Use Daily at Multiple Times when polling frequently (e.g., webhooks not available).
See related topics: How to Create a Flow in Wiresk, How to Run a Flow.
Explore our User Guide.