An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
The source that reported this swap keeps whether it completed, not what went wrong. The step that stopped it is written in each party's own copy of the swap, and those reach SwapScope only for swaps a node it reads happened to relay. For this one, neither party's record is held here.
That the swap did not complete is still a fact about it, and it is counted as one. Nothing was lost by either side: an atomic swap that stops refunds both.
Only completed swaps are checked against a chain, because the check asks whether the agreed trade actually settled. This one did not complete, so there is nothing of that kind to confirm.
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.