So, not sure how new it is but we hit our max licences a few times a week, since we had a cluster locked and require restarting back on the 13th it seems Cloud picked this moment to enable enforced licencing for API connections.
so, if your Now Critical for business Network Edge Agent can’t get a licence as you are on max licences it will simply stop printing.
anyone else have this?
Knowledge Search Articles - EpicCare
note updated 13th July 2026
Wow why should the network edge agent require a license? Running on prem never required an ADDITIONAL license to print, the user who is sending the print job already had to have a license to send the job in the first place. And the fact that you can’t assign a dedicated license to a critical service makes it even crazier.
Just to quote the KB
The Network Edge Agent requires a valid license transiently during each API request, using the username defined at installation.
As with any REST API request, it does not maintain a persistent session and thus may not appear in the Session list.
Therefore, the license usage is brief but frequent, which can lead to license limit errors if close to the maximum number of licenses.
Ensuring you stay below the license limit prevents the error.
Just buy some spare licenses, problem solved 
Epicor will be happy to sell them to you.
Seriously?!?!?!? If 10 people print at the same time that will consume 10 licenses? Does this also apply to things like label printing or EDI receipts/submissions?
Is this why printing/print preview are an absolute nightmare for me right now? Constant helpdesk tickets complaining about printing. We can fluctuate between 5-10 available licenses but between all the printing a company does, finance, purchasing, sales, shipping, jobs you could use up a pile of licenses at any given time.
You know what else would prevent the error? Being able to assign a dedicated service license to the network edge agent so it isn’t competing in the same pool with interactive users.
Just a quick note: Nothing has changed in edge agent around how it works with licensing in the product on the server or client and there is no cloud configuration options to change the base product capability at this time.
The KB article is valid as of now as are the comments about a dedicated license
what I think has changed of the 13th is it’s now being enforced, no-one in their right mind had it that their NEA print servers now needed a licence
what’s crazy is we’ve been having disconnect issues, so the disconnected users still have an active licence and when staff reconnect you now can’t print.. salt in your wounds aye.
nothing changed in the code, probably the KB was updated to be more specific for how REST works with licenses
out of interest I checked our logs and there is the same sporadic message and we’ve obviously never noticed.
anyone aware of if you are hitting this, does the print job not work at all or it does come out after the licence is available again?
Suppose I should be putting up an Epicor Idea’s to smooth out some of this licensing stuff with named users for services or maybe a named pool for printing services?
If a client is using Epicor to print, the NEA should use that same license, not a different one. Probably not doable, but in a better world…
Apparently you can bind your NEA’s to a Service license which we’re investigating now.. we want to understand how this all works IE can we get a pool of licences, what’s the retry period if it does not get a license etc