IBM webMethods Integration Flow Pilot: A Beginner's Guide
Supplemental #3: Known Limitations and Workarounds
Type: Supplemental Article
Read Time: ~5 min
Difficulty: Beginner
Prerequisites: None
Product Page:IBM webMethods Integration Flow Pilot
New to Flow Pilot? Start with the Introduction: What Is Flow Pilot? before continuing.
What This Article Covers
This article documents four known limitations of the Flow Pilot extension and Flow Script Language workflow as of Service Designer 12.1. These are not bugs to report - they are current behavioral constraints of the toolchain that affect how you work. Understanding them upfront will save time during development.
Limitation 1: Service Upgrades in Service Designer Are One at a Time
Service Designer 12.1 does not currently support upgrading multiple existing Flow Services simultaneously. There is currently no batch upgrade option at the package or folder level. However, Service Designer plans to support package level upgrades in future updates.
Currently, if you have a package with ten services that need to be brought into the AI-assisted workflow, each service must be exported and processed individually. There is no shortcut.
What this means in practice: Budget time for this process proportional to the number of services in your existing IS deployment. For teams with large existing deployments, see Supplemental 2: Upgrading Existing Flow Services for the per-service export process.
Limitation 2: "Deploy FlowService" Cannot Update a Service In Place
The Deploy FlowService command does not overwrite or update an existing service on Integration Server. If you attempt to deploy a service that already exists in IS under the same name and namespace, the deployment will not replace it and you will receive an error.
The correct process for updating a deployed service via the Flow Pilot extension is:
- Delete the existing service from IS using Service Designer
- Deploy the updated
.flow file using the Deploy FlowService command
This applies every time you make a change to a service that is already deployed. Alternatively, you may copy and paste the updated service from your agent into the "Source" tab of your existing service in Service Designer 12.1.
Note: Before deleting a service, confirm it is not referenced by any other running services or scheduled tasks in your IS instance. Deleting a service that is in active use may break those dependencies.
Limitation 3: The Extension May Not Recognize All Agents
The Flow Pilot extension may not detect the presence of some AI agents - for example, if an agent has gone through an update that changes how it presents itself to extensions, or if it is running in a configuration the extension does not recognize.
When this occurs, the extension cannot automatically place skill files into the agent's workspace directory. The skills will not be available to the agent automatically.
The workaround is to install the skill files globally. This ensures the skills are available regardless of whether the extension detects the agent. The process for global skill installation is covered in Supplemental 1: Setting Up the Skills with Your Own Agent.
If the extension does not recognize your agent, global installation is the recommended path.
Limitation 4: The Skills Directory is Automatically Added to Every Local Workspace
When an agent is recognized by the enabled Flow Pilot extension, the directory containing the Flow Pilot skill files is automatically added to every local workspace that agent opens. This happens on workspace open.
If you work across multiple projects and only want the Flow Pilot skills active in specific workspaces, this behavior may be disruptive.
The way to stop this behavior is to disable the Flow Pilot extension and then select Enable (Workspace) for Flow Pilot in the specific workspaces you want the directory added. This acts as a per-workspace toggle.
Summary
| Limitation |
Workaround |
| Existing service upgrades to Flow Script in Service Designer 12.1 are done one at a time - currently no batch or folder-level option |
Process each service individually; see Supplemental 2: Upgrading Existing Flow Services |
| Deploy FlowService cannot update an existing service in place |
Delete the existing service in IS first, then deploy the updated file |
| Extension may not recognize all agents (e.g. after an agent update) |
Install skill files globally; see Supplemental 1: Setting Up the Skills with Your Own Agent |
| Skills directory is automatically added to every local workspace for recognized agents |
Disable the extension and then re-enable in workspaces where you want the skills directory injected |
These are current constraints as of Service Designer 12.1 and the Flow Pilot extension at the time of writing. Check the Flow Pilot release notes for updates.
Series Home: IBM webMethods Integration Flow Pilot: A Beginner's Guide
IBM webMethods Integration Flow Pilot: A Beginner's Guide - Supplemental #3: Known Limitations and Workarounds