Last updated
Was this helpful?
Last updated
Was this helpful?
Recurring Transactions Execution History module allows users to monitor and analyze the performance of recurring transactions within the system. Every time a recurring transaction is executed, the module stores comprehensive logs that provide insights into the transaction’s execution status, outcomes, related messages, scheduled times, and any errors encountered. This helps users keep track of recurring transactions, troubleshoot issues, and optimize performance.
Regularly reviewing the Recurring Transactions Execution History helps users:
Identify error patterns or recurring warnings.
Detect transactions with unusually long execution times, which may indicate potential performance bottlenecks.
Make informed decisions on managing or resolving failed transactions, ultimately ensuring smooth and efficient transaction processing.
To access the execution history logs, users must first select the specific job they wish to review. By default, the Recurring Transactions Execution History module displays the activity history for all jobs (transactions) within the system. However, for a more focused analysis, users can utilize the "Select Job" dropdown menu to filter and view the execution history of a particular job.
After selecting a job, users will be able to view the activity logs associated with that job. The logs are categorized into two distinct sections: Logs and Errors.
The "Logs" section provides comprehensive details about all the transaction executed, both successful and with errors. The "Errors" section focuses on transactions that encountered issues during execution.
The Recurring Transactions Execution History module provides flexible options for managing transaction errors by allowing users to mark multiple transactions as "Resolved" or "Unresolved" simultaneously. In the Error logs section, users can find options to Resolve or Unresolve errors for selected transactions.
Resolve: This option allows users to mark specific transactions as resolved. To resolve transactions, users simply select the transactions they wish to mark as resolved and apply the Resolve action. This helps keep the error logs updated and allows users to focus on unresolved issues that still need attention.
Unresolve: This option is used to revert transactions previously marked as resolved back to an unresolved state. This is helpful if further investigation is required or if a resolution is deemed incomplete. By selecting previously resolved transactions and applying the Unresolve action, users can return these transactions to the error list for additional review.
Name
This field displays the name or identifier of the recurring transaction. It allows users to quickly recognize and differentiate among various recurring jobs within the system.
Current Status
This field displays the status of the transaction, "Active" or "Completed".
Execution Dttm
This field captures the exact date and time when the transaction was last executed.
Execution Result
This field provides the outcome or result of the transaction execution, detailing whether it was successful or encountered issues. If there were errors, the Message column may include specific information about the nature of the error, aiding in troubleshooting.
Next Execution Dttm
This field indicates when the next scheduled execution of the transaction will occur. This allows users to anticipate future runs and plan around them, especially if recent executions encountered issues.
Message
This field includes additional details related to the execution, such as informational notes or warning messages.
Is Resolved?
This field indicates whether any issues related to the transaction have been resolved.
Action
This field is available in the "Errors" logs. Click on the "Tick" icon under this column to resolve the error log. Please note that if the "Do not show resolved exports" option is selected, the resolved transactions will be hidden from the error logs.