How to Unlock a Transaction

   Journey Manager (JM) The transaction engine for the platform. |   System Manager / DevOps |   21.05 This feature was updated in 21.05.

Manager allows you to configure a form space as well as a form version with the Save Challenge Lockout Minutes property, which is the duration in minutes a submission is locked out when the maximum number of save challenge requests has been exceeded. This property can be set to 0, which makes a form transaction permanently locked out. In this case, you need an administrator to manually unlock it.

Another option is to unlock a form transaction using an API. Unfortunately, Manager doesn't have any setting or a Fluent API to unlock such a transaction, so the only way to do this is by using Core API Groovy code.

To unlock the transaction with a script:

1. Copy the following Groovy script to the Groovy console.

   import com.avoka.fc.core.dao.DaoFactory
   import com.avoka.fc.core.entity.Submission
   import org.apache.cayenne.access.DataContext
   
   Submission submission = DaoFactory.submissionDao.getSubmissionByTrackingNumber("9367VSY")
   submission.setSaveChallengeFailures(0)
   submission.setSaveChallengeLastFailure(null)
   DataContext.getThreadObjectContext().commitChanges()

2. Update the tracking code with the transaction reference you want to unlock.
3. Click Execute Script.

After you unlocked the transaction, update the Save Challenge Lockout Minutes property either on a form space or a form version level to make sure it will not happen again.

Next, learn how to a configure form space email template.