--- title: Configuring Playbooks slug: configuring-playbooks docTags: createdAt: 2026-09-04T16:49:53.875Z --- Use playbook configuration to define how a playbook starts, what it runs, and how flows connect. Most trigger types are added from the Solution Builder canvas. **DateTime field triggers** are an exception: they are created from a **Date/Time** field in Application Builder and then appear on the selected flow as a system-managed trigger. ## Choose Your Path | **I want to…** | **Start here** | | ---------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- | | Understand trigger types | [Triggers](docId\:SEDgtHtXrZuOHZSUvHAD4) | | Schedule a flow from a Date/Time field value | [Select Fields and Assign Field Properties](https://docs.swimlane.com/select-fields-and-assign-field-properties#datetime-field-triggers) | | Add a DateTime field trigger on the canvas | Not available — configure from Application Builder field settings; see [Triggers](https://docs.swimlane.com/triggers#datetime-field-trigger) | | See which triggers can share a flow | [Flow Sharing Rules](https://docs.swimlane.com/triggers#flow-sharing-rules) | | Review missing Inputs, Outputs, Errors, Required, Sensitive, Type, or discovered outputs | [Review Missing Action Properties](./#review-missing-action-properties) | | Use cron or recurring schedules | [Schedule Triggers](https://docs.swimlane.com/schedule-triggers) | | Start from a record create, update, or delete | [Record Event Triggers](https://docs.swimlane.com/record-event-triggers) | | Start from an external HTTP call | [Webhook Triggers](https://docs.swimlane.com/webhook-triggers) | | Start from a button | [Playbook Button Triggers](https://docs.swimlane.com/playbook-button-triggers) | | Chain flows together | [Flow Event Trigger](https://docs.swimlane.com/flow-event-trigger) | ## DateTime Field Triggers and Scheduled Playbook Flows Starting in **Turbine 26.3.0** (SLA Tracking Phase 1), you can run a playbook flow at a specific time based on a record **Date/Time** field: 1. In **Application Builder**, select a **Date/Time** field. 2. Under **Advanced** → **Trigger Playbook**, click **Configure**. 3. Set **Offset**, **Unit** (**Minutes** or **Hours**), and the target **playbook** / **flow**. 4. Save the dialog, then **save the application**. 5. Turbine adds a **DateTime field trigger** to the selected flow. The trigger details are read-only on the canvas and point back to the field settings. When records are created or updated, Turbine schedules, reschedules, or cancels runs so the flow fires at the field value ± offset (maximum absolute offset: **7 days**). When the DateTime field trigger fires, the playbook receives the **full record** (not tracking ID only), so you can map field values from the trigger output like a **record event** trigger. A DateTime field trigger cannot share its flow with a playbook button, correlation, or another DateTime field trigger. Playbook buttons and correlation may share a flow. See [Flow Sharing Rules](https://docs.swimlane.com/triggers#flow-sharing-rules). :::hint{type="warning"} Deleting a playbook or flow that is linked to a Date/Time field trigger configuration clears that configuration from the application field and cancels outstanding schedules. Confirm the impact warning before you proceed. ::: Full configuration and lifecycle details: [Select Fields and Assign Field Properties](https://docs.swimlane.com/select-fields-and-assign-field-properties#datetime-field-triggers) and [Triggers](https://docs.swimlane.com/triggers#datetime-field-trigger). ## Review Missing Action Properties Starting in **Turbine 26.3.3**, Canvas walks you through actions whose **Inputs**, **Errors**, or **Outputs** schema references are missing. Connector actions, HTTP, Script, Transformation, Emit Event, Create Variables, Update Variables, record actions, Condition, and Loop can appear in the review. Playbook and component runs do not change. You review the flagged settings, then save the playbook. Canvas does **not** include these in the walkthrough: - **Parallel** and **Action Group** wrappers - Read-only canvas nodes - Actions inside an expanded component (review those on the component canvas) On a component, Canvas reviews only the first playbook on that component. ### What Canvas Flags as Missing The coachmark names only the sections that are broken on that action, in this order: **Inputs**, **Errors**, **Outputs**. | What is missing | What to review | | -------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | | **Inputs** | **Required**, **Sensitive**, and **Type** on highlighted input properties | | **Outputs** | **Required**, **Sensitive**, **Type**, and **discovered outputs** | | **Errors** | **Required** and **Sensitive** on error properties | | **Discovered outputs** | Re-test the action, add the outputs again, and mark **Sensitive** as needed. This guidance appears only when **Outputs** is broken. | | Create, Update, or Upsert Record | Selected record fields. Re-select the **Application** and the fields if any are missing. These actions do not use **Required** or **Sensitive**. | | Delete Record | Standard **Inputs** review (**Required** and **Sensitive**) | If no section is identified, the coachmark says **Review configuration for missing required, sensitive.** HTTP can appear in the walkthrough. HTTP does not use the JSON Editor Type recovery used on other actions. ### Start and Pause the Review 1. Open the playbook on the canvas. 2. If actions need review, Canvas opens **Configuration details need to be reviewed**. The dialog says: - **Check if any inputs or outputs should be marked as Required or Sensitive.** - **Check if any discovered outputs are missing. To recover them, re-test the action, re-add discovered outputs, and mark them Sensitive as needed.** - **Configuration appears to be missing. This does not affect playbook or component execution. It only impacts editing and the Run Document view.** 3. Click **Proceed** to start, or click **Cancel** to pause. **Cancel** keeps **Resume** available. 4. On each action, the coachmark uses one of these messages: - **Review Inputs for missing required, sensitive.** - **Review Errors for missing required, sensitive.** - **Review Outputs for missing required, sensitive, and discovered outputs.** - **Review Inputs and Errors for missing required, sensitive.** - **Review Inputs and Outputs for missing required, sensitive, and discovered outputs.** - **Review Inputs, Errors, and Outputs for missing required, sensitive, and discovered outputs.** - **Please verify the selected record fields. If any fields are missing, re-select the Application and the fields.** 5. Click **Configure** or **Edit**, or click **Skip**. **Configure** opens Action Properties. **Edit** opens the side panel. | Action | Broken section | Coachmark button | | ------------- | ------------------------------------ | ---------------- | | Condition | Any | **Edit** | | While Loop | **Inputs** (delay, duration, limit) | **Configure** | | While Loop | **Outputs** or **Errors** | **Edit** | | For Each | **Inputs** (Contains sensitive data) | **Edit** | | For Each | **Outputs** | **Configure** | | Other actions | Any | **Configure** | If an action has more than one broken section, Canvas prefers **Configure** when any section uses **Configure**. 6\. If more than one action remains, use the coachmark arrows to move between actions. 7\. While the review is active, click **Pause** in the canvas toolbar (next to **Test** and **Save**). 8\. After **Pause**, **Skip**, **Cancel**, selecting another action, or adding or pasting an action, the toolbar shows **Resume**. 9\. Click **Resume**. The same **Configuration details need to be reviewed** dialog appears. Click **Proceed** or **Cancel**. ### Review Highlighted Properties 1. Open the action. Missing properties have a yellow highlight. 2. Read the toast titled **Configuration details need to be reviewed**. 3. For most actions, the toast includes: - **Review the highlighted properties as configuration appears to be missing. Check if any of them should be marked as Required or Sensitive.** - **Set the Type where the blue type icon is available. Property types can only be changed before clicking Apply.** - **Check if any discovered outputs are missing. To recover them, re-test the action, re-add discovered outputs, and mark them Sensitive as needed.** - **This does not affect playbook or component execution. It only impacts editing and the Run Document view.** 4. On a component action, the toast omits **Required**, **Sensitive**, and discovered outputs. 5. When you open **Edit** (side panel, While Loop panel, or Loop outputs), the toast is **Configuration appears to be missing. Check if any inputs or outputs should be marked as Required or Sensitive.** If Canvas already knows which section is broken, that toast uses the same **Review Inputs / Errors / Outputs** wording as the coachmark. 6. On Create, Update, or Upsert Record, the toast says **Please verify the selected record fields. If any fields are missing, re-select the Application and the fields.** 7. Set **Required** and **Sensitive** on each highlighted property as needed. 8. Where a blue type icon appears, set **Type**. Hover text: **Set the property type. You can do this only before you click Apply.** 9. If discovered outputs are missing, click **Test**, add the discovered outputs again, and mark **Sensitive** where needed. 10. Click **Apply**. 11. In the **Configuration details need to be reviewed** confirm dialog, verify the following, then continue: - **Please verify each highlighted property's Type and its Required and Sensitive options.** - **Properties with a changeable type will default to Object if left unchanged. This cannot be updated later.** - **Some discovered outputs may also be missing. To recover them: re-test the action, re-add discovered outputs, and mark them Sensitive as needed.** - **Once changes are applied, the highlights and warning messages will no longer appear.** 12. After every flagged action is reviewed, Canvas shows **Configuration review complete**: **All flagged configuration has been reviewed.** and **Save your changes so the updated settings are persisted.** 13. Click **Save** to persist the playbook, or click **Close** to stay on the canvas without saving. You can still update **Required** and **Sensitive** later. You cannot change **Type** after **Apply**. :::hint{type="info"} If you pause the review and copy an action or flow before you finish, later review repairs only the original action. The pasted action can stay out of the coachmark list. Finish the review on the original action before you copy, or delete the pasted action and copy again after the review is complete. ::: ## Related Topics - [Triggers](docId\:SEDgtHtXrZuOHZSUvHAD4) - [Select Fields and Assign Field Properties](docId\:fNGazWp7NqsNvSudl8NBh) - [Application Builder](docId:6Q6Y4_02L_v2KhN80GmO5) - [Organizing Playbook in the Canvas](https://docs.swimlane.com/organizing-playbook-in-the-canvas) - [Create and Modify Playbooks with Hero AI](https://docs.swimlane.com/create-and-modify-playbooks-with-hero-ai)