Technical Tip: Fixing the error 'latin-1 codec can't encode character '\\u2013' in position 21: ordinal not in range(256)'
| Description | This article describes the steps to overcome the failure of the FortiSOAR playbook due to Unicode Characters used in the Playbook name. | ||||||||||||
| Scope | FortiSOAR. | ||||||||||||
| Solution | If the playbook step fails with error: 'latin-1 codec can't encode character '\\u2013' in position 21: ordinal not in range(256)'. Verify if the playbook name consists of the Unicode character EN DASH (–) in it, and modify it with a hyphen instead if required. Similarly, as per the Unicode, check the Characters and modify them accordingly. Below are some common examples that may be introduced when names are copied:
In case the issue persists, feel free to reach out to Fortinet Support for assistance. |
