hedera-services
hedera-services copied to clipboard
(3/18 04:15) expected 'INSUFFICIENT_ACCOUNT_BALANCE', got 'SPENDER_DOES_NOT_HAVE_ALLOWANCE'
Description
Hashscan tx here
---- CryptoTransfer DIFFERED (TRANSACTION_RECORD_MISMATCH) ----
Mismatched values, expected 'INSUFFICIENT_ACCOUNT_BALANCE', got 'SPENDER_DOES_NOT_HAVE_ALLOWANCE' - Matching field 'status' Matching field 'receipt' ==> expected: <INSUFFICIENT_ACCOUNT_BALANCE> but was: <SPENDER_DOES_NOT_HAVE_ALLOWANCE>
For body,
transactionID {
transactionValidStart {
seconds: 1710735417
nanos: 305833884
}
accountID {
accountNum: 1064038
}
}
nodeAccountID {
accountNum: 4
}
transactionFee: 1000000000
transactionValidDuration {
seconds: 120
}
memo: "SentX Bulk Purchase (HBAR) of 1 NFTs (1/1)"
cryptoTransfer {
transfers {
accountAmounts {
accountID {
accountNum: 692010
}
amount: -600000000000
}
accountAmounts {
accountID {
accountNum: 1064038
}
amount: 10500000000
}
accountAmounts {
accountID {
accountNum: 1223480
}
amount: 1500000000
}
accountAmounts {
accountID {
accountNum: 3394401
}
amount: 588000000000
}
}
tokenTransfers {
token {
tokenNum: 4970613
}
nftTransfers {
senderAccountID {
accountNum: 3394401
}
receiverAccountID {
accountNum: 692010
}
serialNumber: 5138
is_approval: true
}
}
}
➡️ Expected Receipt status: INSUFFICIENT_ACCOUNT_BALANCE
exchangeRate {
currentRate {
hbarEquiv: 30000
centEquiv: 342346
expirationTime {
seconds: 1710738000
}
}
nextRate {
hbarEquiv: 30000
centEquiv: 341712
expirationTime {
seconds: 1710741600
}
}
}
but was status: SPENDER_DOES_NOT_HAVE_ALLOWANCE
exchangeRate {
currentRate {
hbarEquiv: 30000
centEquiv: 342346
expirationTime {
seconds: 1710738000
}
}
nextRate {
hbarEquiv: 30000
centEquiv: 341712
expirationTime {
seconds: 1710741600
}
}
}
Steps to reproduce
Run 15 mins events on round 165592765
Additional context
No response
Hedera network
other
Version
v0.48
Operating system
None
This issue still exists. I don't know why it was closed. Reopening.
Is this a case of error check reordering? cc: @tinker-michaelj @Neeharika-Sompalli
This issue still exists. I don't know why it was closed. Reopening.
when I run it on April 5th I didn't see this issue
I reran it yesterday and duplicated the error