---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Input variable removal

# Input variable removal {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

Deleting workflow input variables, like insert and update actions, creates a customer
update record in a user's current update set.

These deletions migrate to a new instance with the update set, regardless of whether the
workflow that owns the input variables is published in the same update set. Plan carefully and
use caution when editing a workflow and selecting update sets.

## Input variable removal risk {#ariaid-title2}

An existing workflow already contains two input variables.
1. The workflow was migrated to a production instance with the two variables.
2. On a development instance, User A selects Update Set A and checks out the workflow.
3. User A removes one input variable and all references to it in the workflow.The
   system enters into Update Set A one customer update record reflecting the deletion of
   the input variable. No record is added for the new workflow version which no longer
   depends on the input. This does not happen until the workflow is published.

4. User A continues working on other features in Update Set A that need to be moved to production.
5. User A completes Update Set A and migrates it to the production instance without publishing the workflow.The update set entry that deletes the workflow input variable
   now applies to the production instance. The prior version of the workflow is running
   on this instance and still references the missing variable.

{#r_InputVariableRemovalRisk__ol_ap4_jmz_gr}

## Input variable removal solution {#ariaid-title3}

When editing workflows, particularly when deleting input variables, be sure to use a
single update set for all variable editing and workflow publishing.
If necessary, merge the update set into a more general set targeted for deployment after
the workflow is published. For information about update sets, see [System update sets](https://www.servicenow.com/docs/access?context=system-update-sets&version=australia&pubname=australia-application-development&ft:locale=en-US).  
Hinweis:  
If a workflow version is already running on a production system and input variables are deleted from a newer version, those deletions could affect transactions already running against the earlier version. Use extreme caution when deleting workflow input variables and plan the migration carefully.

## Input variable removal prevention {#ariaid-title4}

Prior to publishing a workflow version, the system validates the workflow model to
assist the designer in planning for deployment.
This validation warns of critical errors that can prevent a workflow from running
successfully, but also warns of dependencies and conflicts in update sets. See [ValidateUpdateSetDependencies](https://servicenow-prod.fluidtopics.net/bzaiSFe39SdbtH4wnhZCSw "The ValidateUpdateSetDependencies validator identifies all the subflows called in the current workflow and determines if any of those subflows are being edited in a different (in progress) update set.") for more details.