Skip to main content
Employee
October 21, 2026

KB-2419 Custom smart service plug-in deployment fails with APNX-1-4104-005 error due to local-id collision between plug-ins

Symptoms

  1. Custom plug-in fails to deploy via direct upload through the Admin Console Plug-ins page.
  2. The following error message is displayed in the Admin Console: Unable To Deploy Plug-in - Plug-in failed to deploy.
  3. Stack trace shows IncompatibleSmartServiceRegistrationException with error code APNX-1-4104-005:
    ERROR com.atlassian.plugin.manager.DefaultPluginManager - There was an error loading the descriptor 'sampleEncryptPIIData' of plugin 'com.sample.encrypt'. Disabling.



    com.atlassian.plugin.PluginException: com.appiancorp.suiteapi.common.exceptions.AppianRuntimeException: com.appiancorp.process.admin.IncompatibleSmartServiceRegistrationException: The Smart Service Module was invalid: Smart service input and output count does not match the count for the existing smart service registered as <local-id> (APNX-1-4104-005)

     

  4. Log message indicates: Newer plugin smart service com.sample.encrypt.SampleEncryptionSmartService overriding older plugin.

Cause

The issue occurs when deploying a custom smart service plug-in that uses a local-id attribute that collides with an existing plug-in's smart service, causing a smart service parameter count mismatch. The local-id attribute is only required when migrating custom smart services built for prior Appian versions and should not be set for net-new plug-ins. For more information on this error, see Custom Smart Service Plug-ins - Deployment Issues.

Action

  1. Open the appian-plugin.xml file within the custom smart service plug-in source code.
  2. Remove the local-id attribute from the <smart-service> element.
  3. Recompile the plug-in JAR file.
  4. Resubmit the plug-in to the AppMarket for approval.
  5. Deploy the approved plug-in via Direct Upload in the Admin Console.

For more information on the local-id attribute, see Custom Smart Service Plug-ins - Configuring the appian-plugin.xml File.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2026