---
sourceDocument: Xanadu ServiceNow AI Platform Administration
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/platform-administration

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu ServiceNow AI Platform Administration

ft:clusterId :

    - platadm

bundleId :

    - platadm

workflow :

    - Platform


---

# Specifying the inbound email processing order

# Specifying the inbound email processing order {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

You can configure a processing order for inbound email actions and use the order to
manage multiple filters in inbound email actions.
The Ordered Email Processing (com.glide.email_ordered_processing) plugin is enabled by
default for new instances. Users with the admin role can activate the plugin for upgraded
instances. The plugin adds the Order column to the Rules \[sysrule\]
table, which the instance uses to determine when to process emails. Admins can also add a
command to an action script that halts processing after the script runs.

## Configure the processing order {#ariaid-title2}

Configure the processing order for inbound email actions to force them to run in a
prescribed order.

### Before you begin

Role required: admin

### Procedure

1. Navigate to AllSystem PolicyEmailInbound Actions.
2. Open an existing inbound action or create one.
3. Complete the form and assign an order number to the Order field to establish when this inbound rule should run in relation to other rules.  
   If you upgraded and activated the plugin, the Order field might be named Execution Order.  
   Note:  
   Ensure each inbound action has a unique Order value to ensure the system stops processing as expected. If multiple inbound actions have the same Order value, the system might evaluate all of the inbound actions, even if one of them contains the `event.state="stop_processing";` script or has the Stop processing option selected.
4. To stop rule processing when an inbound email action runs successfully: add the following line to the bottom of the script:  
   * Select the Stop processing check box.
   * Add the following line to the bottom of the Actions script:

         event.state="stop_processing";

   {#t_ConfigureTheProcessingOrder__ul_ec2_ytl_3v}

## Manage multiple filters in an inbound email action {#ariaid-title3}

Use process ordering and the stop_processing command to manage multiple filters in inbound email actions.

### Before you begin

Role required: admin

### About this task

In this example, you can create new problem records when prb:
appears in the subject line and new change requests when chg:
appears in the subject line. All other emails are used to create an incident. The
actions are set up as follows:

### Procedure

1. Create an action with a condition of Subject \> starts with \> chg: and the `event.state="stop_processing";` command appended to the script.
2. Assign this action an Order value of <kbd class="ph userinput">100</kbd>.
3. Create an action with a condition of Subject \> starts with \> prb: and the `event.state="stop_processing";` command appended to the script.
4. Assign this action an Order value of <kbd class="ph userinput">200</kbd>.
5. Create an action for incident with no conditions and an Order value of <kbd class="ph userinput">300</kbd>.  
   It is not necessary to add the stop_processing command to
   the script for the incident action unless you want processing to stop at
   this rule to avoid continuing to another action.

### Result

If either a change request or a problem is created, the
stop_processing command stops processing, and no incident
record is created. If neither a change request nor a problem is created, the inbound
email action for incident creates a record.

*[\>]: and then