#1101 Jbidwatcher decides not to snipe (good) without warning (bad

[Anonymous]

I recently had a multisnipe going, and the first item that ended was not bid on, presumably because of a communications error. It ended lower than my sniping price. Oh well, sometimes happens. I assume it's because my computer is old and overworked, and something (JBidwatcher?) seems to have a memory leak. I didn't investigate this further.
Hours later, another snipe of that same multisnipe set was due. It wasn't bid on either! I looked in the article history, and read that JBidwatcher had intentionally not sniped since it couldn't determine the status of a previously sniped-on auction and decided not to risk buying two items.
That's fine with me, except I would have liked a warning pop-up or something. Perhaps even an additional configuration setting to decide whether to snipe anyway.

I don't ever look in the article history, so I would seriously have liked an obvious warning about this situation (which had existed for, I believe, 22 hours at this point). The whole point about using JBidwatcher is to have less to worry about, after all. And in general, it does an outstanding job, so keep up the good work!

I will be leaving for a two-year trip(!) on Thursday. If you would like to view logs or anything, please contact me before then as I will otherwise have to drill through the earth's core in order to get them :)

If you wish to contact me, my email is homegrown ät gmx dot net.

Best regards,
Luca