Checking a TON payout when the send action was skipped
A wallet processed a signed request, but the merchant cannot find an outgoing payment. The compute phase and the action that creates an outbound message are separate parts of the wallet transaction.
Inspect the send mode and action result
Mode 3 includes the flag for paying forwarding fees separately and the flag that allows certain send errors to be ignored. The local fixture represents one skipped action with zero created messages. Successful processing of the external request alone cannot prove the transfer happened.
const mode = 3;
console.log(Boolean(mode & 1), Boolean(mode & 2));
const action = { total: 1, skipped: 1, messagesCreated: 0 };
console.log(action.messagesCreated > 0);
Follow the outbound message to its destination
Inspect action-phase counters and the actual outgoing messages. For a batch, identify the specific destination, value and payload being reconciled: another successful message may have come from the same wallet transaction. If the expected message exists, follow it to the recipient for the final application outcome. If the action was skipped, preserve the request and trace before making a retry decision. The ignore-errors flag covers selected errors and does not guarantee every malformed request can complete.