A couple of sites on Mosaic 24.1.0.0 have found they can't check more than 985 invoices at a time. We're still exploring whether the 985 limit applies to all sites or just those that discovered the issue. This might affect you if you have a particularly large payment run with up to 1000 invoices or more.
This error will show up as a ‘500 internal server error’, so it won't hit the typical database log table or framework logs.
Workaround
Please try the following workaround in your test environment, assuming you have a cycle of 1,000 invoices:
Click Check All, but don't save yet.
Uncheck enough invoices so you're only checking 985 of them.
Save the check.
If it works, great! You'll need to reject the rest of the unchecked invoices to proceed with certification. Then, create a new payment cycle to pick up those rejected invoices and repeat the process.
If this works, that’ll be the solution for production.
Permanent Resolution
To prevent this from happening in future runs, you'll need to set the system property INV_PER_PAYMENT_CYCLE to a value that allows you to certify all invoices. If 985 didn't work then you may want to reduce it further or uncheck more from the cycle when you have checked all to begin with.
Alternatively, if you do want a higher number of invoices based on the highest number of invoices you would ever expect to see in a payment cycle then you will need to changed the Wildfly setting called Max Parameters to a suitable value. This value will be about 50 above what you have in your System_Properties for INV_PER_PAYMENT_CYCLE. If you have a value in your system properties for 1000 invoices per cycle, then your Max Parameters will need to have the value of 1050.
If what we have suggested is not working still, then please raise a new case so we can look for other causes or workarounds to resolve the issue. When raising the case, include:
Your Mosaic version.
The Cycle ID.
A full screenshot of the Payment Cycle summary screen.
Whether this can be replicated on a test instance.
If self-hosted, the framework logs on DEBUG level from the point you click Save to confirm this isn’t another cause of the issue.