Purchase Kanban in Public Cloud 2025.2 not always triggering through minimum

Our Pilot database has been upgraded to 2025.2.5 and in our testing we’ve found Purchase Kanban not triggering through the minimum quantity on the Warehouse.

We have been using this for years with no issue in previous versions. We can get it to trigger a new PO release if we increase the on hand and decrease it by a large amount but we don’t understand what minimum quantity it’s using and different parts behave differently!

We’ve done testing on 60 parts and approxiamtely 10% of our parts do trigger at the correct warehouse minimum but we can’t see any pattern on why it works on these parts and not others.

Could anyone out there on 2025.2 that uses the Purchase Kanban functionality please test a number of your parts and see if you get a similar issue? We use quantity adjustment to increase/decrease through the minimum (but have also tested a standard backflush transaction).

The issue occurs because the system checks for all open releases associated with the PO number linked in Part Maintenance, instead of referencing the specific PO Line to determine whether a new release should be created.
Related problem case PRB0307487