> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/reference-docs/reference/server-configurations/playbook-server-configurations.md). # Playbook Server Configurations Server configurations for playbooks in Cortex XSOAR 6.15. | Key | Description | Default | | ----------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------- | | **`clean.playbook.debug.sessions.interval`** | Changes the automatic termination of debugger sessions (in minutes). Can be used for [debugger troubleshooting](/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-testing.md#UUID-a8a8b77f-afeb-a723-238a-e92fcd790fda). | **`180`** | | **`content.playbooks.unlock`** | Comma-separated playbook names to unlock. | N/a | | **`ignore.default.in.playbooks`** | Whether to allow the **Do Not Use By Default** checkbox to affect playbooks. By default, the Cortex XSOAR playbook does not take **Do not use by default** into account (only for CLI Commands). For example, if you have 3 mail sender instances, 2 of them are set to not use by default, when running the playbook without specifying an instance, it sends with all 3 instances. After you set this configuration to **`true`**, it only sends from the one that is not marked as **do not use by default**. | **`false`** | | **`messages.html.formats.externalFormSubmit`** | [Customizes a Data Collection task](/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields.md#UUID-01759cd2-eb94-25fb-a769-a0a3f544813b). | N/a | | **`messages.html.formats.externalAskSubmit`** | [Customizes an Ask task](/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields.md#UUID-603dd208-534f-90ea-c444-3cceafa2a9b6). Add HTML with your customizations as the value. | N/a | | **`modules.execute.retries.count.maximum`** | Determines how many times the script attempts to run before generating an error in a playbook task. | **`100`** | | **`modules.execute.retries.interval.maximum`** | Determines the wait time (in seconds) between each execution of the script in a playbook task. | **`800`** | | **`playbook.debug.sessions.duration.max`** | The maximum time in hours a debugger session can remain open. Can be used for [debugger troubleshooting](/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-testing.md#UUID-a8a8b77f-afeb-a723-238a-e92fcd790fda). | **`24`** | | **`playbook.loop.max`** | Sets the maximum number of times the playbook loop will iterate, until it stops. | **`100`** | | **`playbook.stuck.notification.users`** | Notifies users when Playbooks fail (comma-separated-user names). | N/a | | **`soc.name`** | Customizes the SOC name in the survey header for an Ask task. For more information, see [Customize the SOC Name](/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-task-fields.md#UUID-c3679253-6687-199f-033a-f25bbb128f4b). | N/a | | **`workers.count.debug`** | Changes the number of workers, when using the Playbook debugger. Can be used in [debugger troubleshooting](/xsoar-6-administrator-guide/6.15/customize-cortex-xsoar/customize-and-configure-cortex-xsoar/playbooks/playbook-testing.md#UUID-a8a8b77f-afeb-a723-238a-e92fcd790fda). | **`1`** | | **`playbook.willnotexecute.old.eval`** | Prevents repeated task checks in playbooks. Do not change to true unless instructed to do so by Customer Support. | **`false`** | | **`active.directory.auth.external.instance`** | When setting up communication task authentication with Active Directory, if you see the error message **could not find a provider to authenticate with**, add this server configuration. The value is the name of your Active Directory instance. | N/a | | **`comm.ask.linktocontext.enabled`** | Whether to add generated links for an Ask task to the Context Data. | **`false`** | | **`comm.datacollection.linktocontext.enabled`** | Whether to add generated links for a Data Collection task to the Context Data. | **`false`** | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.15/reference-docs/reference/server-configurations/playbook-server-configurations.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.