LOCK_IMPORT_SENDOUT group cannot be locked in exclusive mode

The LOCK_IMPORT_SENDOUT  error can be seen when a group has been exclusively locked by another process

The complete message is:

Resource type: LOCK_IMPORT_SENDOUT, instance: group=XYZ cannot be locked in exclusive mode.

Here, XYZ will be replaced by the locked group ID number.

Locked by a running sendout

When a sendout is active, no changes can be made to the group as this could influence the recipient data used by the active sendout. If you search for the group ID from Engage, then go to the group overview, you will see in the group details further information about the lock, including the message ID.

You can then take this message ID and check to see if the message is :

• Currently sending: Wait for the sendout to complete and the lock will automatically be released

• Sending is paused: Unpause the sendout to let it complete, or cancel the sendout to release the lock

Locked by another import

You cannot run multiple consecutive imports into the same group as this would run the risk of conflicting information being executed at the same time on the same data: you will need to:

• Wait for the currently running import to complete and release the lock

• Cancel the running import that will automatically release the lock

If you have no running imports or there are no currently running sendouts, please raise a ticket with Technical Support.

Knowledge Base Reference ID: 202002271318