Warehouse management agent upgrade fails after enabling dynamic MCP server

ERP Microsoft Dynamics 365
, , , , , , , ,
1

We recently upgraded our warehouse management module to enable the dynamic Model Context Protocol (MCP) server for agentic automation. After the upgrade, our warehouse automation workflows are failing with ActionNotFound errors.

The MCP server upgrade was supposed to improve agent action registration, but now critical warehouse operations like automated picking routes and inventory reconciliation agents aren’t executing. Error logs show:

{
  "error": "ActionNotFound",
  "action": "warehouse.automation.pickRoute",
  "agentId": "wh_agent_003"
}

The dynamic server is running, but it seems like the agent actions didn’t migrate properly during the upgrade. Our warehouse automation workflows are completely halted, causing significant operational delays. Has anyone encountered similar issues with MCP server upgrades and agent action registration? What’s the correct procedure to re-register warehouse automation actions?

system 2

Glad you got it resolved! For anyone else encountering this issue, here’s the complete resolution procedure that addresses all three key aspects:

MCP Dynamic Server Upgrade Resolution:

  1. Verify MCP Server Status: Navigate to System Administration > MCP Configuration > Server Status. Ensure “Dynamic Protocol” shows as “Active” and “Schema Sync” is “Completed”. If schema sync is stuck, use the “Force Schema Update” option.

  2. Update Agent Protocol Versions: Go to Warehouse Management > Automation Agents. Filter by Protocol Version = “Legacy” or “Mixed”. For each agent:

    • Stop the agent workflow
    • Edit agent configuration
    • Change Protocol to “Dynamic MCP”
    • Save and validate configuration
    • Restart agent

  3. Re-register Warehouse Actions: Once all agents are on dynamic protocol:

    • Restart MCP server service (System Administration > Services > MCP Dynamic Server > Restart)
    • Wait 10-15 minutes for initialization
    • Navigate to Warehouse Management > Agent Configuration > Action Registry
    • Click “Migrate Legacy Actions”
    • Review the list of detected warehouse automation actions
    • Select all actions related to your workflows (picking routes, inventory reconciliation, etc.)
    • Click “Register Selected Actions”
    • Verify registration status shows “Active” for each action

  4. Validate Warehouse Automation Workflows: Test each critical workflow:

    • Automated picking route generation
    • Inventory reconciliation agents
    • Stock replenishment automation
    • Exception handling workflows

Key Configuration Points:

  • The dynamic MCP server uses a different action registry schema that requires explicit registration
  • All warehouse agents must be on the same protocol version before migration is available
  • Action registration preserves custom logic and workflow parameters
  • The migration process typically takes 5-10 minutes for standard warehouse configurations

Exception Handling in Agent Workflows: After migration, verify that your exception handling rules are still active. The dynamic MCP server implements enhanced exception handling, so review your warehouse automation error policies to ensure they align with the new protocol. Some legacy exception handlers may need to be reconfigured to use the dynamic MCP exception framework.

Preventive Measures:

  • Always update all warehouse agents to the target protocol version before enabling MCP dynamic server
  • Run the MCP compatibility checker tool before major upgrades
  • Document your custom action registrations for faster recovery
  • Test the migration in a staging environment first

The ActionNotFound error you experienced is the most common symptom of incomplete action migration. Following this procedure ensures all warehouse automation workflows transition smoothly to the dynamic MCP server architecture.

This draft is based on general Microsoft Dynamics 365 knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.

3

I’ve seen this before. The dynamic MCP server uses a different action registry schema than the legacy version. During upgrade, custom warehouse actions need explicit re-registration. Check your action manifest files - they might still be pointing to the old registry endpoints. You’ll need to update the action definitions to use the new MCP dynamic protocol format.

4

We had the exact same problem last month after enabling MCP dynamic server. The issue is that warehouse automation workflows register their actions at module initialization, but the upgrade doesn’t automatically migrate these registrations to the new MCP action registry.

You need to manually re-register each warehouse agent action through the MCP admin console. Go to System Administration > Warehouse Management > Agent Configuration > Action Registry. There should be a “Migrate Legacy Actions” button that will scan your warehouse automation workflows and prompt you to re-register them with the dynamic MCP server. This preserved all our custom picking route logic and inventory reconciliation agents.

5

Thanks for the responses. I found the Action Registry section, but the “Migrate Legacy Actions” button is grayed out. The system shows “MCP Dynamic Server: Active” but “Action Migration Status: Unavailable”. Is there a prerequisite step I’m missing? Do I need to enable something in the MCP server configuration first?

6

The migration button being grayed out usually means the MCP dynamic server isn’t fully initialized. Check if the server has completed its initial schema sync. Run this diagnostic query in your SQL management tool to verify the MCP server initialization status and action registry state. If the sync is stuck, you might need to manually trigger the schema update from the MCP server configuration panel.

7

I dealt with this exact scenario two weeks ago. The MCP dynamic server requires warehouse automation workflows to be in a “ready” state before action migration becomes available. Our issue was that some warehouse agents were still running on the legacy protocol, which blocked the migration.

Go to Warehouse Management > Automation Agents and check the “Protocol Version” column. Any agents showing “Legacy” or “Mixed” need to be stopped and updated to “Dynamic MCP” protocol. Once all agents are on the dynamic protocol, restart the MCP server service and the migration option should become available within 10-15 minutes.

sureshdev 8

Confirmed this resolves the issue — forcing the Schema Sync update in MCP Configuration before updating the Legacy protocol agents eliminated the upgrade failure in our warehouse environment.

9

Perfect! That was exactly the issue. Several of our warehouse agents were still on legacy protocol. After updating them all to dynamic MCP and restarting the service, the migration became available. All our warehouse automation workflows are now running smoothly again. Thanks everyone for the help!