Oh, but it does, at least if you do "account_tx account ledger" for a specific ledger id (as opposed to a range).
You're correct. It's kind of a quirk in the code. If you specify a ledger range, special code for ranges of ledgers handles it. If you specify one specific ledger, generic code that fails if the ledger isn't available handles it.
@JoelKatz with the db fix mentioned in the issue I opened everything works great, thank you!
To infinity and beyond!
Now, a small doubt on workflow; I submit a payment for which no trust line exists, I assume this transaction never gets submitted to a ledger, right? At least I could not find my test one. The issue I'm having is one of atomicity, where I submit a tx and note the request ID to match the response, but say between send and response my ws dies, and don't get this response at all.
Can I poll for it afterwards? Or is the assumption that if I don't see it in a ledger for a set period of time I can just resubmit the request? The latter feels dangerous if the network is busy and lags a bit.