The API Co-Signer may not sign transactions if its transaction queue is full. The API logs will include a "queue is full" error in this case. This means that the API Co-Signer's internal queue is overloaded and needs to be restarted. This is separate from your workspace transaction queue.
Resolution
To resolve a full API Co-Signer queue:
- Cancel all the pending transactions.
- Make sure there are no pending requests on the API Co-Signer.
- Restart the API Co-Signer using the following command:
./cosigner restart - Wait a few minutes to confirm that the queue is empty.
- Submit a new transaction.
- Confirm the transaction is signed by the API Co-Signer as expected.
The root cause for the full queue may be related to server CPU capabilities. Confirm that your API Co-Signer server meets the recommended hardware requirements.
Need additional help?
If you have a question or need assistance, contact Fireblocks Support and include the following information in your request:
- Workspace name
- The first four characters of the corresponding API key
- User information (indicate whether the user is an active Co-Signer or is going through initial setup)
Additionally, copy the following logs from the API Co-Signer:
- Transaction handling (/databases/cosigner/log/customer_cosigner.log)
- Transaction signing flow
- Logging the Callback Handler request and response
- Configuration changes to the API Co-Signer (date_time.run.log)
- Setup
- Pairing a new API user
- Changing the Callback Handler URL