Known Issues and Workarounds

copying playbooks and actions copying playbooks and actions does not generate new schemas and webhook urls, which means the copied playbook can remain linked to the original note that any changes made to schemas in one playbook also affect the other additionally, if you delete a webhook in the copied playbook, it also removes the webhook from the original record action when adding fields to the map, make sure to select all the necessary fields the first time if you reopen the map and add new fields later, the previously added fields are removed reports double quotes are not displayed correctly in a report after the page is refreshed records the hover functionality does not work on the record page currently records there is a bug (breaking change) where boolean values (true and false) are no longer automatically mapped to the string values "true" and "false" in selection fields within records workaround instead of using boolean values and expecting the system to map them to the corresponding strings, you need to directly map the strings "true" or "false" during the create/update process ssp export when exporting ssp, a 500 error occurs if any record actions are not configured with an application canvas existing playbooks will not work with canvas compatibility between canvas and existing playbooks will be provided in a future version of turbine condition actions a condition action in a loop with no action in the true path will result in a playbook failure, even after all actions in false path are successful add a dummy action in the true path to ensure the playbook has the correct result new error message for records mapping values to selection fields that do not match the available options will now cause the action to fail, though all other fields will still be mapped correctly for example, if you pass an undefined value or "swimlane" to a checkbox field that only accepts "hello" or "world" as options, nothing will be set for that field, and the action will fail with an error message for that field therefore, it is advised to ensure that the correct value is being sent or to update the downstream action to trigger on completion