Hi, I set a bid for this item at 25.03, but it ended at 20.50 without any bid on it. It's currently in the 'completed' folder, but with a blue box rather than a red or green one like all the others. What happened here?

Hello Alexander,
Thank you for your question about this item. If I look at the log for this snipe (clicking the log icon next to the snipe), it was added at 22:31:28, and the item ended at 22:34:08.
That is a 160-second difference, which is within the 120 second threshold.
Frankly, I think this should be 180 seconds. Theoretically, I think 90 is the lowest I can go, but right now I'm going to change it to 180.
Thanks for the report as it resulted in an improvement. Let me know if you have any other questions.

Ok thanks for the response. Didn't care that much about the item but was more concerned about the snipe. Appreciate your work.

Thank you as well, your understanding is appreciated.

LOL, what an understatement I just made. I don't normally discuss other customers, but I did have another customer write in with the F-bomb. I haven't seen an F-bomb in years... and in the subject, no less.
I didn't realize how close to the end that people were adding snipes! I now see that there was a very, very heavy load, and it needed just a few extra seconds advance notice.
Well, thanks again as it still amazes me how new situations come up.

Yeah if it's super important to me I'll generally try to snipe it myself just in case lol.
Btw, it just failed again, and I definitely got this one in in time...
Item # 186421304772
Is there a new bug? Never had this issue before. Lmk, thanks.

The time difference on that one is 4 minutes and 18 seconds.
And I had a third person write in, this one was close to 5 minutes also.
The temporary solution is to change the threshold to 5 minutes. I did so. This will give me time to add some more logging and understand this.
The April 22 update was a tenfold increase in stability, so I'm guessing this is a one-line code fix somewhere. I'll let you know when I have an answer.

Got it, thanks for the response! I just know that I used to really push the limits with how much time left I set the snipes and they always seemed to work lol. Probably save me some $ if I need to set them earlier haha.

You bet.
Check out the Slam-It tab, there is is something there you might want to try out. If you have feedback, feel free to open a new thread.

p.s. The issue turned out to be a quick fix, as I said. We have the snipe engine set to load no more than 500 snipes per minute.
So nowadays there are buyers that use AI to write scripts that use our API. "Write me a script to snipe an item using BidSlammer's API," and then they put it into Excel or AppleScript or whatever. Then they mass-snipe the popular $0.99 items.
It's all part of the service, so I increased it to 2000 until the next world event.

Hmmm it appears to have happened again. Item number: 126472472209.
Originally set snipe to 80.08, then increased to 88.08 with I believe around 6 min left (but def more than 5) and it finished at 85 without a snipe. Again, not a big deal as it was at the upper end of my snipe anyways so I don't mind not winning lol, but just letting you know.

This time I caught it. I re-wrote the whole job scheduler code as a result.
I can't believe that bug has been there for probably a decade ... just now rearing its head (see above). It explains a lot.
I need a day or two to test before I release. I set the threshold set to 10 minutes until then. I'll let you know.