From d919c11126a16314b3b0116db72100e1e65b7df9 Mon Sep 17 00:00:00 2001 From: Malware Utkonos Date: Thu, 11 Dec 2025 12:23:28 -0500 Subject: [PATCH] Add language about workflow ephemerality. Fixes #7771 --- docs/dev/workflows.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/dev/workflows.md b/docs/dev/workflows.md index 61d6b77fc..349551223 100644 --- a/docs/dev/workflows.md +++ b/docs/dev/workflows.md @@ -195,7 +195,7 @@ Once you've queried the available workflows, you can create your own by cloning #### Example: NOP'ing Module-Level Analysis -The following example demonstrates how to modify a module workflow by clearing all module-level analysis. This effectively disables module-level analysis while preserving the ability to analyze single functions at a time in the UI. +The following example demonstrates how to modify a module workflow by clearing all module-level analysis. This effectively disables module-level analysis while preserving the ability to analyze single functions at a time in the UI. Don't worry about registering the cloned workflow over top of `core.module.metaAnalysis`. Workflows are all generated fresh when Binary Ninja opens. They are then modified by plugins. Any changes you make here will not be there next time you start Binary Ninja. ```python # Clone the workflow