What is a transaction

What is a transaction

A single transaction represents the entire end-to-end flow of a journey. A transaction occurs every time a journey is triggered, irrespective of the outcome (Succeeded, Pending, or Failed) or the number of steps involved. Each activation of the journey, regardless of its complexity, duration, or the number of steps counts as a single transaction.

Consider a journey where customer feedback entered into a Google Sheets spreadsheet automatically triggers the creation of a support ticket in Freshdesk. This process includes capturing feedback details in the spreadsheet, mapping these details to corresponding fields in Freshdesk, and creating the ticket.

The entire sequence - from logging the feedback in Google Sheets to creating the ticket in Freshdesk - constitutes one complete transaction. Here's a look at how a transaction looks in this scenario. There are three transactions listed here, with two marked as Succeeded and one as Failed.

• The transaction details for a journey that is triggered when a new row is added to a Google Sheets spreadsheet, leading to the creation of a new ticket in Freshdesk is as follows:
  1. Status: This column displays the outcome of each transaction. It shows Succeeded for transactions that were completed successfully, Failure for one that did not complete as expected, and Pending for transactions that are still in progress.
  2. Repeated: The Repeated status in the transaction report is triggered when the Rerun button is clicked, indicating a re-execution of the journey. This allows you to identify when the transaction has been processed multiple times under the same conditions. In this case, all entries show No, indicating that each transaction was a unique trigger event.
  3. Description: This column provides a brief description of the transaction and is auto-generated.
  4. Time: The time column logs the exact time each transaction was processed, that can help in tracking and auditing the journey's activities.

Note:
A journey may be in a Pending state during execution due to multiple steps that require time to complete. Here are common reasons a journey remains pending:

• Complex calculations or large data volumes that need processing.
• Delays in responses from external APIs, such as ticket creation in Freshdesk.
• Waiting for specific conditions to be met in decision-making processes.
• Waiting due to custom delay action in Scheduler by Quickwork app.
• If there is any step of type Ask a question, and the transaction is waiting for the user's answer or his input.

These factors can keep a journey Pending until all necessary operations are finalized, which will eventually resolve into either Succeeded or Failed.