Optimizing Webgility Desktop Scheduler for Timely and Efficient Order Processing
This article helps Webgility Desktop users in understanding and resolving issues where the scheduler processes orders slowly and starts earlier than expected. It documents the investigation steps and clarifications needed to identify underlying causes and optimize scheduler performance for timely and efficient order processing.
Issue Overview
The scheduler is processing orders slowly and starting earlier than expected. This article documents the investigation and clarification process.
Reviewing Scheduler Performance
- Analyzed scheduler logs to determine order processing time.
- Identified that each order is processed in approximately 7-10 seconds, which is within normal operating parameters.
Steps:
- Access Scheduler Logs:
- Navigate to the server or application's logging directory.
- Open the latest scheduler log files for the affected date.
- Review Processing Time:
- Search for entries indicating when each order was picked up and completed.
- Calculate elapsed time for several orders to confirm processing speed.
Understanding the 'Run at Startup' Setting
- The Run at Startup setting is designed to trigger order processing whenever the application starts, regardless of scheduled times.
- This explains early execution if the application is launched manually later than usual.
Steps:
- Verify Scheduler Configuration:
- In the admin interface, go to the computer Settings.
- Locate the Run at Startup toggle or checkbox.
- Reason:
- When enabled, the scheduler initiates as soon as the app launches—potentially causing earlier or out-of-schedule order processing.
Resolution Steps
- Understood normal processing duration in the computer.
- Checked the impact of the Run at Startup setting on order processing times.
- Verified that no further assistance was needed.