Work with requests

Overview

  • Understand the possible statuses of requests. A request is submitted for approval whenever you create/edit/delete/revoke the following Objects: Transactions, Users, Accounts, Groups, Whitelists, and Admin rule.
  • Once a request is approved, it goes through different statuses. For example, if you requested the revocation of a user, they'll be revoked once all approvals have been collected. The status of the user will go from Active to Pending revocation, and then Revoked.
  • Be aware of Requests limitations.

Transaction requests status

The status of a transaction request is displayed in the Status column of the transaction page. This table describes all possible statuses.

Status Description
Awaiting approval You haven't reviewed the request and your approval is required.
Pending approval You've approved the request, but additional approvals must be collected.
Approved

One of the following reasons applies:

  • The necessary number of approvals has been collected, but the transaction hasn't been broadcasted.
  • The necessary number of approvals has been collected, but the HSM failed to sign the transaction.
Signed The transaction has been signed by the HSM but the wallet daemon failed to broadcast it.
Submitted The transaction has been approved and broadcasted to the blockchain network. It hasn't received any confirmations yet.
Confirmed The transaction has received its first confirmation from the blockchain network. We recommend waiting for more confirmations to consider the transaction as completed.
Failed The transaction couldn't be broadcasted because the account's transaction rules have changed or the approval workflow is invalid. It must be recreated.
Failed to broadcast

The transaction couldn't be broadcasted because of connection issues with the Wallet Daemon. When this status appears, the transaction won't be broadcasted again. You must recreate a transaction.

Rejected An Operator has rejected the request.
Dropped

The submitted request has been rejected by the blockchain. This can happen when:

  • the blockchain has been reorganized.
  • double-spending UTXOs.
  • the wrong nonce was used to send the transaction (Ethereum only).
Expired The request hasn't been approved before the 7-day expiry date.

Requests status

Requests can have different statuses as described in the following table.

  Request name Possible status
Users
  • Create Operator
  • Create Administrator
  • Revoke user
  • Awaiting approval: Your approval is required on the request.
  • Pending approval: You've approved the request and more approvals must be collected to authorize it.
  • Approved: The request has been approved.
  • Rejected: An Administrator has rejected the request.
  • Failed: The request has failed because it conflicts with a request that has just been authorized. See the section below for additional information.
  • Expired: The request hasn't been approved or rejected within the allocated time period: 7 days.
  • Pending registration: (user requests only) An invitation URL has been sent to the user and you're now waiting for them to register.
Accounts
  • Create account
  • Edit account
Groups
  • Create group
  • Edit group
  • Delete group
Whitelists
  • Create whitelist
  • Edit whitelist

Additional information on the Failed status

Failed is the status given to requests that were interrupted because they conflict with another request which has just been authorized.

Requests limitations

Occasionally, you'll be prevented from creating a request because it conflicts with another request pending approval. This request will first have to be approved or rejected to allow you to create the new one. Below is a summary of possible use cases.

Objects

Objects (Users, Accounts, Groups, Whitelists, and Admin rule) can have the following statuses.

Object type Object status

Users

  • Pending registration: An invitation URL has been sent to the user and you must wait for them to register.
  • Pending: A new Operator or Administrator is being created. Additional approvals are pending to be collected to activate the user.
  • Active: The Administrator or Operator is active and can operate in your workspace.
  • Active Ÿ : The Administrator or Operator is active but a revocation request is in progress. If it's authorized the user will be revoked.
  • Access suspended: The Operator has been temporarily suspended.
  • Revoked: The Administrator or Operator has been revoked from your workspace.

Accounts

  • Pending: A new account is being created. Additional approvals are pending to be collected to activate the account.
  • Active: The account is active and can be used to create transactions.
  • Active Ÿ : An edit request is in progress on this account. If it's authorized the edits will be implemented.
  • View-only: The approval workflow of the account (Ethereum or ERC20 only) hasn't been provided. For more information, see View-only Ethereum accounts.

Groups

  • Pending: A new group is being created. Additional approvals are pending to be collected to activate the group.
  • Active: The group is active and can be used in the approval workflow of any account.
  • Active Ÿ : An edit or deletion request is in progress on this group. If it's authorized the group will be edited or deleted.
  • Deleted: The group has been deleted.
Whitelists
  • Pending: A new whitelist is being created. Additional approvals are pending to be collected to activate the whitelist.
  • Active: The whitelist is active and can be used in the transaction rules of any compatible account.
  • Active Ÿ : An edit request is in progress on this whitelist. If it's authorized the whitelist will be edited.
Transactions
  • Pending: A new transaction is pending. Additional approvals must be collected before it's approved.
  • Approved: The transaction has been approved and broadcasted to the blockchain network.
  • Rejected: The transaction has been rejected by an Operator.