Run chains

After you publish a chain, you can run it to perform its commands:

• To run a chain without a set schedule, run it manually.
• To have a chain run automatically, set its schedule.
• To automatically run a chain based on an event in a connected solution, use a trigger event.
• To start a chain after another chain completes, use the Run Chain event to string them together.

Manually run a chain

To manually run a chain, select it in your workspace, and then click Execute flight_takeoff and Run Chain.

Note: To stop a chain's run, click Stop. When you stop a chain that includes Run Chain events, you also stop any chains' runs started by those events.

Schedule when to automatically run a chain

To automatically run a chain on a routine basis or during a specific date range, add and set its schedules.

1. In the chain, click Chain Settings.
2. Under Schedules  alarm , click Add  add.
3. Select the timezone for the schedule, and enter the time to run the chain.
4. Under Frequency, select how often to run the chain, such as every few hours or once monthly.
5. To run the chain during only a specific time period, enter its start and end dates.
   • To run a chain indefinitely, choose a start date and then click the X next to the end date.
6. Click Apply, Save, and Publish.

After you add a schedule, you can manage when it runs:

• To temporarily stop a chain from starting at a set time, click Disable Schedule  visibility for the schedule.
• To update a set frequency, click Edit  create for the schedule.
• To remove a schedule, click its Delete  delete.

Note: For updates to a chain's schedule to take effect, click Publish.

Start a chain based on a trigger event

To automatically run a chain based on an event in a connection solution, start it with a trigger event:

• To start a chain based on a BlackLine® Journal Service event, such as a new certified journal entry, use the BlackLine Journal Service trigger event.
• To start a chain when a File Utils connector detects an event—such as Create, Modify, or Delete—in a file directory, use the File Events trigger event.
• To start a chain when an HTTP Request connector detects a POST event with a JSON payload, use the HTTP Webhooks trigger event.

When using trigger events, keep the following in mind:

• Chains can't be scheduled when a trigger event is used.
• Only one trigger event can be used per chain.

View a chain's history

To view previously published versions of a chain in Chain Builder, go to the Chains  device_hub tab and select Versions from the individual chain's menu. For each past version, you can view when it was created, and by whom.

To view a chain's run history, such as to troubleshoot an error:

1. From Chain Builder, click Monitor flight_takeoff.
2. Search for a chain by name, or use the filters at the top of the screen to narrow your results by:
   • Status
   • Time
   • Date
   • Workspace/environment
   • Connections
   • Tags
3. For each run, you can view chains details including its status, who ran it, and its start and end times.
4. For more details about the run, click its row and inspect each command during the run. For each command, you can view its outputs, inputs, and error log during the run.
5. To view all runs for the chain, click Run History.

Analyze chain usage

To track and analyze the usage and success of your chains in Chain Builder, from Home home, select the period of time to analyze.

Note: To focus on chains within specific environments in your workspace, click Filter , and select the environments to analyze.

From Home, you can monitor:

• Chain Results, for how many chains succeeded, failed, or resulted in a warning during the set time period.
• Activity Feed, for an audit log of updates to chains during the set time period, including who makes the change and when.
• Command Stats, to track how many commands run during the set time period.

To update a metric with the latest activity, click Refresh refresh.