Abandoned Transactions

   Journey Manager (JM) Previously known as Transact Manager (TM).  |    System Manager / DevOps  |  v5.1 & Higher This feature is related to v5.1 and higher.

A submission can be completed or abandoned. Manager considers abandoned transactions as completed transactions, so they can be purged. Abandoned transactions can also be configured to deliver data depending on a threshold value, which determines how incomplete form data was before the transaction became abandoned. Manager stores abandoned submissions along with all other transactions that are part of the transaction life cycle.

Transactions can be abandoned automatically or manually.

Automatic abandonment can happen under varying conditions depending on your Manager configuration:

  • 24-hour interval for transactions which are rendered but never actually captured any data or transactions which are never saved by a user, even though they are background saved by Maestro Editor or using the Form.backgroundSave() Maestro API.

    You can't change this 24-hour abandonment policy time interval.

  • Data retention policy, which determines how long a saved transaction is maintained in Manager before it is automatically abandoned.
  • Tasks with configured expiration time are abandoned after this time has elapsed. If no expiration time is set, then the save abandonment time is used.
  • Forms with abandonment delivery can have a more aggressive abandonment policy than the standard 24 hour policy.

Manual abandonment can come from:

Next, learn how to view submissions history.