How to Fix Webgility Desktop Crashes When Re-Downloading Orders
This article helps Webgility Desktop users resolve crashes in Webgility Desktop that occur when re-downloading orders, particularly in environments with limited RAM and large databases. The guide provides step-by-step instructions to check the software version, optimize application settings, evaluate system performance, and manage the database efficiently to prevent future crashes.
1. Confirm Your Webgility Version
Make sure you’re using the latest supported version of Webgility:
-
Open Webgility.
-
Go to Help > Terms & Conditions.
-
If you're not on the latest version, follow the prompts to upgrade.
2. Adjust Download Settings
Large order volumes can overwhelm your system. To reduce strain:
-
Go to Connections > Sales Channel > Advance Settings.
-
Limit the date range or reduce the number of orders downloaded per batch.
-
Save your changes and try re-downloading.
3. Check System Resources
Systems with large order databases should have at least 16 GB of RAM. To monitor performance:
-
Open Task Manager (Windows) or Activity Monitor (Mac) while re-downloading.
-
Look for high memory usage or any performance slowdowns that may indicate memory exhaustion.
4. Clean Up Your Database
A large database can contribute to crashes. To optimize:
-
Navigate to Orders > Archived Orders.
-
Remove or archive older orders you no longer need.
-
Always back up your database before making deletions.
5. Test After Optimization
Once you’ve upgraded RAM or cleaned up your database:
-
Attempt the order re-download again.
-
Confirm that Webgility runs smoothly without crashing.
6. Verify QuickBooks Data Integrity
After re-download, if still issues found - Check QuickBooks connection