Deposits completed but polaris says they failed about django-polaris HOT 5 CLOSED

Hi @nikita-gorodeckij,

Polaris doesn't use the submit response because Polaris supports using third-party custodians. So if I use Polaris for my anchor but I use Circle or Fireblocks for my custody, I won't have a submit response, I'll just have the transaction hash.

from django-polaris.

But if this is what you're seeing in the application's behavior, you might be right. Let me follow up with the Horizon team to see if this is likely.

The fix would be to retry the request until the transaction is found. If the transaction isn't found have X retries or Y seconds, fail. What do you think?

from django-polaris.

Wait @nikita-gorodeckij, in your example, ea393ff2-e8bf-4f0b-bcb1-2f919feb952b is not a valid transaction hash or ID. Trying to fetch a transaction with this ID would certainly fail.

from django-polaris.

@JakeUrban It is not transaction hash. It is valid uuid. It should be output of this line

from django-polaris.

Hi @nikita-gorodeckij, you're right about the transaction ID, my mistake. Have you been experiencing this issue still?

from django-polaris.