When things slow down, you don’t have to guess what’s wrong. AimBetter quickly shows what is causing the ERP to drag, so the team can fix it fast, saving time, headaches, and costly outside help. Here’s a recent real case that shows how it worked for one of our new customers.
A growing company runs a web-based Priority ERP system (On-Prem, Web, and API) that’s central to their daily operations, managing everything from sales orders and inventory tracking to purchasing, accounting, and customer service. Their ERP also shares data with third-party apps through an API—one of which is a cloud SaaS that automates processing and compliant storage of supplier invoices for their accounting system.
For some time, employees had been complaining about significant slowdowns, particularly in the morning and midday, when business activity is at its peak. Timeouts started impacting critical business processes, frustrating users and IT alike. The IT team couldn’t identify the cause—it felt like searching for a needle in a haystack.
Making the Invisible Visible
After installing AimBetter, the answer came fast. With real-time visibility, the team could immediately see web requests that were taking a long time to complete—along with their full URL, which made it clear they were coming from the third-party invoice-processing SaaS.
After installing AimBetter on the application server, web server, and database, the picture became clear in no time.
AimBetter’s real-time monitoring showed slow API requests, complete with the full URL, program, and parameters, clearly pointing to the third-party invoice-processing SaaS.
AimBetter revealed that many of these requests were accessing very high amounts of cached data each time (on average, 18 GB), along with a high average duration, which is a clear red flag.
Drilling down, the team discovered why: a missing date filter in the API queries. Instead of retrieving only the relevant transactions, the calls were pulling entire large tables.
The third-party provider wasn’t even aware of this—although they had included what they thought was the date parameter in their code, a format mismatch meant it wasn’t actually used, and a default value of 0 was being set instead.
With AimBetter, it was also possible to see the exact process from the third-party application and monitor the execution rate per minute. The data showed that it never exceeded 10 tasks per minute—likely a limit set by the API—yet the volume of data retrieved in each task was still enormous due to the missing date filter.
Clear Insights, Fast Action
With this info in hand, the company reached out to the SaaS provider. The third-party team, impressed by AimBetter’s clarity, fixed their code.
⚠ Problem 1 – Excessive API Calls at Night
The company was running 50 sub-companies inside a single Priority instance, all triggering API calls simultaneously overnight.
✅ Solution: The software vendor split processes across different times for each sub-company, reducing extreme load and preventing retries from timeouts that spilled into the workday.
⚠ Problem 2 – Missing Query Limitations
Each API call was fetching thousands of records, on average 18 GB at once.
✅ Solution: The vendor updated the API to apply proper date filtering and reduced the batch size from 4,500 records to 500 records per request, easing server pressure and reducing timeouts.
The Results
- ERP performance was restored immediately.
- One whole month of stability without a single user complaint.
- Smooth business operations with zero interruptions.
- A stronger collaboration with the SaaS provider, who was impressed by the clarity AimBetter delivered.
The difference was immediate. ERP performance bounced back, users were happy again, and API traffic became much lighter.
Simple Visibility Leads to Big Results
This story shows how AimBetter empowers IT teams to spot and fix complex performance problems quickly. By making the unseen visible, AimBetter saved time, prevented frustration, and helped build stronger collaboration with their third-party partner.
