Check compatibility of Subflow or Action
After establishing the ACL, publish the component and check the compatibility staging table.
Before you begin
Role required: admin
Procedure
Go to Workflow Studio and publish the Subflow.
You can also run a full compatibility scan via the scheduled job.
Open the compatibility staging table for the relevant Subflow.
Locate your component by name or sort by updated date.
Verify all the three compatibility columns: security_compatible = true, data_compatible = true, execution_compatible = true.
The overall status should read as compatible. If security_compatible is false, the other columns will show N/A (not applicable). The system uses a fail-fast approach, fix security first, then re-check.
Republish the component after making ACL changes for re-evaluation.
Once marked as compatible, the component can be added to an MCP server as a tool.
What to do next
Subflows must be activated for AI use in Flow Designer to be available as MCP tools. Open the subflow, go to Manage Security, enable Callable by Client API, and add a Client Callable Flow Object ACL with execute permission. Skipping this step will prevent the subflow from appearing in the tool creation list.
Parent Topic:MCP Server Console reference