Builds being rejected for no reason?

We have imported applications that support multiple versions, so the application is set to allow for multiple active releases. This works 90% of the time, but then at times I get messages like this:

This build was rejected on 12/8/2014 5:03:46 PM by [user, usually me, sometimes system].
Superseded by new build.

But there is no new build on that release, as I refresh one release (create new build) another one has its build rejected. It feels random but it feels like it happens to a few of them quite often.

I don't know if there is another setting or trigger that would have cross-release build rejections, if so please point me to it. If not then I think there is a bug here.

Thanks,
Dan

Product: BuildMaster
Version: 4.4.7

Thank you for the analysis - we were able to reproduce this and as you experienced, it only seems to happen 1 out of every 10-20 times.

There is really only 1 place where builds are rejected, and that happens to be in a stored procedure so once we find a fix we can send you a patch. The fix will also be included in v4.5.7.

Actually as it turns out, this was unintentionally happening in two places, and only if Multiple Active Builds was disabled.

Here is a zip file that contains a SQL script (valid only for BuildMaster versions 4.1.0-4.5.6) that you can run against the BuildMaster database to stop the invalid rejection:

http://44.inedo.com/buildmaster/RejectBuildPatch.zip

Executed with output of:
(1 row(s) affected)

(1 row(s) affected)

Will let you know if I see any more problems like this,
Thanks for the incredibly fast turn around time!