ACC - Delivery in Start Pending State

 1) Check whether the Delivery is scheduled:

The Pending status can first mean that your delivery has been scheduled and is pending until the given date. For more on this, refer to the Delivery scheduling section.

2) Check MTA Process Status:

The MTA (Message Transfer Agent), which runs modules and processes on the delivery server, and which manages email sending, may have not been started, or may need to be restarted.

To check this and to start the module, if necessary, apply the following steps:

a) Check that your mta@<instance> modules are launched on your MTA servers.

     nlserver pdump

      mta@<INSTANCENAME> (9268) - 23.0 Mb

b) If the MTA is not listed, start it with the following command:

nlserver start mta@<INSTANCENAME>

NOTE: Replace <INSTANCENAME> with the name of your instance (production, development, etc.). The instance name is identified via the configuration files: [path of application]nl6/conf/config-<INSTANCENAME>.xml

3) Review Delivery affinity Setup:

The delivery may be using an affinity not configured on the sending server.

In this case, check the configuration of the traffic management (IP affinity) and use the Managing affinities with IP addresses field to link deliveries to the MTA that manages the affinity. For more information on affinities, refer to this section.

4) Increase NmsOperation_LimitConcurrency:

When too many campaigns are running, the delivery status remains in ‘Pending’ status.

The limit of simultaneous campaigns is defined in the NmsOperation_LimitConcurrency option. The default value is 10.

NmsOperation_LimitConcurrency should be increased gradually by 10. The value should not be more than 50. For reflecting the changes done to the NmsOperation_LimitConcurrency option please restart OperationMgt workflow.

Learn more about options on this page.

If the issue is still occurring, please contact Adobe Campaign Support