Troubleshooting-record-creation-or-update-fails-with-field-field-name-must-have-value-turbine-26.5.1
Troubleshooting: Record Creation or Update Fails with "Field <field name> must have value" (Turbine 26.5.1+)
Environment & Versions
- Product: Swimlane Turbine
- Affects Versions: 26.5.1 and later
Overview & Problem Statement
Starting in Swimlane Turbine 26.5.1, Swimlane strictly enforces required field validations across both manual user interactions and automated flows (such as playbooks, connectors, API record creation, and webhook ingestion).
Before version 26.5.1, certain conditional required field validations configured in application workflows were enforced primarily during interactive UI sessions, allowing automated ingestions to bypass them if an affected field was left blank. With Turbine 26.5.1, background automation flows and manual submissions adhere to the same validation engine: any record creation or update attempt without a required value will fail immediately.
Symptoms
During record creation or record updates via the Turbine UI or automated playbook actions, the action fails with the validation error:
Field <field name> must have value.
In playbook execution logs, the record action terminates with a failure status and records this validation message in the execution output.
Cause
This error indicates that a field evaluated as mandatory was left empty during record creation or update. This occurs due to one of two configuration reasons:
- Static Field Requirement: The field is globally configured as Required in the application form settings.
- Conditional Workflow Validation: An Application Workflow action dynamically marks the field as required because its trigger conditions evaluated to true. This frequently happens when:
- Another field that drives the condition contains a default value upon record creation (evaluating the rule to true immediately when the record initializes).
- The incoming automation payload does not supply a value for the conditionally required field.
Resolution Procedure
Follow these steps to locate and resolve the validation failure:
Step 1: Identify the Affected Application and Field
- Inspect the error message or playbook run execution output to identify the exact <field name> cited.
- Identify the target Application where the record creation or update is occurring.
Step 2: Check Static Field Settings
- Open the target application in the application builder.
- Locate the field referenced in the error message and open its configuration/properties.
- Check if the field is set as Required:
- If marked Required: Determine if the field must be mandatory across all contexts. If it should not block automated intake or initial creation, clear the Required setting, save the application, and re-test.
- If NOT marked Required: The requirement is being applied dynamically via workflow logic. Proceed to Step 3.
Step 3: Inspect Application Workflow Actions and Conditions
- Navigate to the application's Workflow configuration.
- Review the configured workflow actions to find the rule setting the errored field to required.
- Check the rule's Trigger Conditions:
- Identify which field and value satisfy the condition (e.g., [Status] = "Triage" or [Condition Field] = "Value").
- Check whether any controlling fields have default values configured in the application field. A default value is assigned the moment a record is created, which will immediately trigger any workflow actions tied to that value.
Step 4: Update the Workflow or Field Defaults
Choose the solution that best fits your workflow design:
- Solution 1: Remove or adjust the default value on the controlling field If the controlling field defaults to a value that prematurely fires the requirement during automated creation, remove the default value so newly initialized records remain blank until populated.
- Solution 2: Refine the workflow condition Update the workflow rule conditions to only make the field mandatory at appropriate lifecycle stages (e.g., when a status is moved beyond initial creation or when an analyst updates the record), allowing empty values during record intake.
- Solution 3: Provide the value in automation If the field must remain mandatory at creation, update the playbook action or integration mapping to supply a valid value when the record is created.
Investigation Case Study: CIM Application
Scenario
In a Case & Incident Management (CIM) application, automated phishing ingestion playbooks began failing after upgrading to Turbine 26.5.1 with:
βField Outcome must have valueβ
Root Cause Analysis
- The Outcome field was not statically marked as required in the field settings.
- An application workflow rule was configured to make Outcome mandatory when:
- False Positive = No
- The False Positive field was configured with a default value of No.
- Before 26.5.1, automated playbook creation bypassed this conditional check. In 26.5.1, the validation was strictly enforced for automation. Because the record initialized with False Positive = No, Outcome immediately became mandatory, causing the playbook record creation to fail because Outcome was empty.
Resolution Options Tested
- Option A (Field Default adjustment): In the development environment, removing the default No value from the False Positive field allowed new records to initialize without firing the mandatory rule, and record creation succeeded.
- Option B (Workflow Condition adjustment): The workflow condition was modified to only require Outcome when a record moves to an investigation or closed state, allowing initial automated record creation while still enforcing the requirement for analysts closing tickets.