Skip to content

Scheduling Flows

This guide explains how to schedule flows to run automatically at defined intervals—daily, weekly, or at custom times.

Before scheduling a flow:

  • You must have a saved flow ready to schedule
  • An admin must have enabled scheduling for your tenant (one-time setup)
  • You need to complete a one-time authorization (see below)
  1. Generate a JWT access token

    Follow the Machine-to-Machine OAuth guide to:

    • Create an OAuth Client Application in Alation (requires Server Admin role)
    • Generate a JWT access token using client_id and client_secret
  2. Register the OAuth app for scheduling

    Call the registration endpoint with your admin JWT token:

    Terminal window
    curl -X POST "https://your-alation-instance.alationcloud.com/ai/api/v1/oauth_app/register" \
    -H "Authorization: Bearer <admin_jwt_token>" \
    -H "Content-Type: application/json"

    A successful response confirms scheduling is enabled:

    {
    "success": true,
    "message": "OAuth app registered successfully"
    }
  3. Verify scheduling is available

    Users should now see the Authorize button in the Schedule tab instead of a disabled state.

Scheduled flows run without you being logged in, so the system needs permission to act on your behalf. This is a one-time setup.

  1. Open a flow and navigate to the Schedule tab

  2. You’ll see an “Authorization required” message

    Schedule tab showing authorization required message

  3. Click Authorize

    Schedule settings dialog with Authorize button

  4. Complete the authorization in the popup window

  5. You’ll see a success confirmation

    Schedule tab after successful authorization

Once authorized, you can create schedules for your flow.

  1. Open your flow and go to the Schedule tab

  2. Click + New schedule

  3. Configure the schedule settings:

    New schedule dialog with configuration options

  4. Click Save

SettingDescription
FrequencyHow often to run (Daily, Weekly, Monthly)
Days of weekFor weekly schedules, which days to run
TimeWhat time to run (in your local timezone)
Runtime parametersValues to pass to the flow’s inputs
EnableToggle to activate or pause the schedule

The dialog shows a preview of when the flow will next run.

After creating a schedule, it appears in the Schedule tab:

Schedule list showing created schedule with details

The schedule list shows:

  • Summary — Human-readable description (e.g., “Weekly on Monday at 9:00 AM PST”)
  • Run count — How many times the schedule has triggered
  • Last run — When it last executed and whether it succeeded
  • Enable toggle — Quickly enable or disable without deleting

Click on a schedule to edit its settings. You can change the frequency, time, or runtime parameters.

Toggle the Enable switch to pause a schedule without deleting it. The schedule retains its configuration and can be re-enabled at any time.

Click the actions menu (three dots) and select Delete to remove a schedule permanently.

Scheduled runs appear in the flow’s Runs tab alongside manual runs. Each run shows:

  • When it executed
  • Whether it was triggered by a schedule or manually
  • Status (Completed, Failed, Running)

Click any run to see detailed step-by-step execution logs.

IssueSolution
Authorization expiredRe-authorize in the Schedule tab
Schedule disabledCheck the Enable toggle
Flow has validation errorsFix errors and save the flow
Scheduling not availableAsk your admin to complete the admin setup

If you see “Authorization failed” in run history:

  1. Go to the Schedule tab
  2. Click Authorize to refresh your credentials
  3. Complete the authorization flow

If a scheduled run fails with a “schema mismatch” or similar error, it means an agent or tool used in your flow was modified after the flow was created.

What causes this:

  • An agent’s output fields were renamed or removed
  • A tool’s required inputs changed
  • The agent or tool was deleted entirely

How to fix it:

  1. Open the flow in the editor
  2. Check each step for validation errors (usually highlighted)
  3. Update the variable mappings to match the new inputs/outputs
  4. Save the flow and re-run