Transaction working but saying not validated

[Tomram]

To the experts out there I have a question.

I'm making a transaction that has been created in a wallet in an offline mode on a computer that never gets connected to the internet. The validated transaction file (text file) is then used to make the transaction on a computer that is connected to the internet. When submitting the transaction it gives me the message that the transaction is unable to be validated by the network, but it is in fact going through. I can see at the destination (an exchange) that the transfer has taken place.

I've done numerous transactions like this in the past with no issues. This is the first time I've seen the this response.

Can someone explain to me what is happening and if there is any danger to the transaction?

Thanks in advance.

[KarmaCoverage]

What are you using to create the TX blob?

What validator service are you using?

[nikb]

53 minutes ago, Tomram said:

To the experts out there I have a question.

I'm making a transaction that has been created in a wallet in an offline mode on a computer that never gets connected to the internet. The validated transaction file (text file) is then used to make the transaction on a computer that is connected to the internet. When submitting the transaction it gives me the message that the transaction is unable to be validated by the network, but it is in fact going through. I can see at the destination (an exchange) that the transfer has taken place.

I've done numerous transactions like this in the past with no issues. This is the first time I've seen the this response.

Can someone explain to me what is happening and if there is any danger to the transaction?

Thanks in advance.

You’ll need to provide more information. Do you have the transaction hash?

[SquaryBone]

If you're using the bithomp transaction explorer: this seems to be broken. It worked in the past but now transactions do process but are still "not found" or something similar.

[Tomram]

I've PM'd nikb about the transaction. In a nutshell when I explore the transaction hash it says it was successful, which makes sense because the XRP I transferred made it to the destination. It was at the time of the transaction where I would normally see the result being 'success' where I had the result that it couldn't verify the transaction. I'm using the Ripple Desktop Wallet, which I've used for years with no issues. Nikb is unsure as to the reason for the error.

[TaylorWarden]

On 6/28/2020 at 3:40 AM, Tomram said:

I've PM'd nikb about the transaction. In a nutshell when I explore the transaction hash it says it was successful, which makes sense because the XRP I transferred made it to the destination. It was at the time of the transaction where I would normally see the result being 'success' where I had the result that it couldn't verify the transaction. I'm using the Ripple Desktop Wallet, which I've used for years with no issues. Nikb is unsure as to the reason for the error.

The default settings of the Ripple Desktop Wallet have you connect to the s-west.ripple.com:443 or s-east.ripple.com:443 servers to interact with the RCL.  Sometimes I notice that these servers do not connect or lose connection then reconnect shortly after sometimes.  My fix for this was to set s1.ripple.com:443 as my server and that was the cure for my issues with that client.

[Warbler]

On 6/28/2020 at 7:58 AM, SquaryBone said:

If you're using the bithomp transaction explorer: this seems to be broken. It worked in the past but now transactions do process but are still "not found" or something similar.

Can you give me some examples?  

[SquaryBone]

12 hours ago, Warbler said:

Can you give me some examples?  

That was posted like more than a month ago.  I had it with a transaction I did. I tried some others from the past that also were processed and had the same issue. The XRP already arrived but still gave me that error. Can't and won't give transaction information  Perhaps it was a temporary thing.