Schedule a Jinba Flow Workflow

Set up a recurring flow run with a cron expression and timezone, then manage its schedule.

Publish the workflow, then set a cron expression and timezone for recurring runs. Scheduled executions use the published version.

Schedule settings in the triggers panel. Run flows automatically at a set interval

Run the published version on a schedule

Jinba Flow allows you to schedule workflows to run automatically at specified times using cron expressions. Scheduled workflows execute the published version, making them perfect for automated tasks, periodic data processing, and scheduled reports.

What is Scheduling?

Scheduling enables automatic execution of workflows:

• Automatic Execution: Workflows run automatically based on a schedule
• Cron Expressions: Use standard cron syntax to define execution times
• Published Version: Scheduled workflows always use the published version
• Timezone Support: Specify timezones for accurate scheduling

Prerequisites

To schedule a workflow:

1. Published Workflow: The workflow must be published (see Publish)
2. Schedule Permission: You need permission to schedule workflows in the workspace
3. Cron Expression: Define when the workflow should run

Setting Up Scheduling

Step 1: Open Workflow Settings

1. Open your published workflow in the Flow Editor
2. Open the Triggers panel
3. Find the Schedule section

Step 2: Enable Scheduling

1. Turn on the Schedule switch (it is disabled with the message “Flow must be published to enable scheduling” until the flow is published)
2. The schedule is created preset to every day at midnight in your browser’s timezone (CRON_TZ=<your timezone> 0 0 * * *); click the schedule to open the form and change it

Step 3: Configure Schedule

1. Enter a cron expression, fill in the minute/hour/day fields, or describe the schedule in plain language and click Parse natural language
2. Select a timezone
3. Review the schedule description and the next run time
4. Click Save Schedule

Step 4: Verify Schedule

1. Check that the schedule is active
2. View the next scheduled execution time
3. Monitor scheduled executions in the execution history

Cron Expressions

Basic Cron Syntax

Cron expressions consist of five fields:

┌───────────── minute (0 - 59)
│ ┌───────────── hour (0 - 23)
│ │ ┌───────────── day of month (1 - 31)
│ │ │ ┌───────────── month (1 - 12)
│ │ │ │ ┌───────────── day of week (0 - 6) (Sunday to Saturday)
│ │ │ │ │
* * * * *

Common Cron Examples

Every Minute

* * * * *

Every Hour

0 * * * *

Daily at Midnight

0 0 * * *

Daily at Noon

0 12 * * *

Every Monday at 9 AM

0 9 * * 1

First Day of Every Month at Midnight

0 0 1 * *

Every 15 Minutes

*/15 * * * *

Every Day at 2:30 AM

30 2 * * *

Weekdays at 9 AM

0 9 * * 1-5

First Day of Every Quarter at Midnight

0 0 1 */3 *

Timezone Support

Specifying Timezone

You can specify a timezone using the CRON_TZ prefix:

CRON_TZ=America/New_York 0 9 * * *

This runs the workflow at 9 AM Eastern Time every day.

Common Timezones

• UTC: Coordinated Universal Time
• America/New_York: Eastern Time
• America/Chicago: Central Time
• America/Los_Angeles: Pacific Time
• Europe/London: Greenwich Mean Time
• Asia/Tokyo: Japan Standard Time
• Australia/Sydney: Australian Eastern Time

Note: Schedules saved from the schedule form always carry a CRON_TZ prefix. A cron expression without one is evaluated in the API server’s timezone, which can differ from the timezone the form displays, so keep the prefix.

Schedule Management

Enabling a Schedule

1. Open the Triggers panel
2. Navigate to the Schedule section
3. Turn on the Schedule switch
4. Configure the cron expression
5. Click Save Schedule

Disabling a Schedule

1. Open the Triggers panel
2. Navigate to the Schedule section
3. Turn off the Schedule switch, or click Disable Schedule in the schedule form
4. The schedule is immediately disabled

Note: Disabling a schedule stops all future executions but doesn’t affect currently running workflows.

Updating a Schedule

1. Open the Triggers panel
2. Navigate to the Schedule section and click the schedule
3. Modify the cron expression
4. Click Save Schedule

Important: Schedule updates take effect immediately. The next execution uses the new schedule.

Scheduled Execution Behavior

Published Version

Scheduled workflows always execute the published version:

• Stability: Uses the stable published version, not your current edits
• Consistency: Ensures scheduled executions use the same version
• Updates: Republish to update the scheduled workflow version

Execution Context

Scheduled executions:

• Source: Marked as “SCHEDULE” in execution history
• Arguments: Use default or empty arguments (unless configured)
• Permissions: Run with workspace permissions
• Logging: All executions are logged in execution history

Execution Monitoring

Monitor scheduled executions:

1. View execution history
2. Filter by source “SCHEDULE”
3. Check execution status and results
4. Review any errors that occurred

Best Practices

1. Test Before Scheduling: Test your workflow thoroughly before scheduling
2. Publish Stable Versions: Only schedule workflows with stable published versions
3. Timezone Awareness: Always specify timezones for accurate scheduling
4. Monitor Executions: Regularly check execution history for scheduled runs
5. Error Handling: Implement error handling in workflows for scheduled execution
6. Resource Management: Consider resource usage for frequently scheduled workflows
7. Documentation: Document schedule purpose and timing in workflow description

Common Use Cases

Daily Reports

Schedule workflows to generate daily reports:

# Every day at 8 AM
0 8 * * *

Data Synchronization

Schedule periodic data synchronization:

# Every 6 hours
0 */6 * * *

Weekly Summaries

Schedule weekly summary generation:

# Every Monday at 9 AM
0 9 * * 1

Monthly Processing

Schedule monthly data processing:

# First day of every month at midnight
0 0 1 * *

Frequent Monitoring

Schedule frequent monitoring tasks:

# Every 5 minutes
*/5 * * * *

Troubleshooting

Schedule Not Running

Possible Causes:

• Schedule is disabled
• Workflow is not published
• Cron expression is invalid
• Workflow is archived

Solutions:

1. Verify schedule is enabled
2. Ensure workflow is published
3. Validate cron expression syntax
4. Check workflow is not archived

Wrong Execution Time

Possible Causes:

• Timezone not specified
• Incorrect cron expression
• Timezone conversion issues

Solutions:

1. Specify timezone explicitly
2. Verify cron expression
3. Test with a simple schedule first

Execution Failures

Possible Causes:

• Workflow errors
• Missing credentials
• Resource limitations

Solutions:

1. Check execution history for errors
2. Verify credentials are configured
3. Review workflow logic
4. Check resource availability

Schedule Validation

Cron Expression Validation

The system validates cron expressions:

• Syntax Check: Ensures valid cron syntax
• Range Validation: Validates field ranges
• Error Messages: Provides clear error messages for invalid expressions

Visual Schedule Builder

Many interfaces provide visual schedule builders:

• Point-and-Click: Select schedule options visually
• Preview: See schedule description before saving
• Validation: Automatic validation of schedule settings

Related Features

• Publish - Learn about publishing workflows
• API - Learn about calling workflows via API
• History and Versions - Learn about execution history