Transactions retries

The transaction_retries model allows setting one parameter.

filters: a dictionary of filters

Note that the output fields are predefined and cannot be changed.The output data is sorted based on the occurrence time of the transactions and then by the attempt number. Sorting is only applied if the date-time filter has a duration of 31 days or less.

`filters`

Filters allow filtering of the transaction retries’ data to be exported.

Value	Type	Validation
`created_at`	`dict[str, str]`	See date-time filter below

No filtersIf no filters should be applied, just set filters as null

Date-time filter

A date-time filter could be defined as follows.

{
    "start": str
    "end": str
}

start and end allow three types of values:

Valid ISO 8601 timestamp with or without timezone. UTC is assumed if the time zone is not specified.
Date-time placeholder to be set dynamically
null: this represents an open range

Validations

The validations below are checked:

start <= end, only when both are timestamps
start and end cannot be null at the same time

Example

Example of report creation using the transaction_retries model.

{
  "name": "Test report",
  "spec": {
    "model": "transaction_retries",
    "params": {
      "filters": {
        "created_at": {
          "start": "2023-01-01T00:00:00"
        }
      }
    }
  }
}

Overview

Integrations

Insights

Monitoring & Alerting

Flow

Roles & Permissions

Reports

Settlement reports

SSO

Transactions retries

`filters`

Date-time filter

Validations

Example

​filters

​Date-time filter

​Validations

​Example

`filters`

Date-time filter

Validations

Example