Skip to content
  • There are no suggestions because the search field is empty.

How to Resolve Scheduler and Order Posting Problems Across Webgility Desktop Installations

This article helps Webgility Desktop users resolve common issues with automation features in Webgility Desktop, particularly in environments where the main server hosts the application and add-on installations run on other systems. It covers troubleshooting for Scheduler tasks, connection permissions between machines, and order posting failures.

Step 1: Adjust Startup Settings on All Systems

Automation can fail if the Scheduler runs on multiple systems instead of only on the main server.

What to do:

  1. Log in to each system running Webgility Desktop.

  2. Open Webgility Desktop.

  3. Click the Scheduler icon (clock) > Settings in the top-right corner of Webgility Desktop

  4. Ensure in Settings > Run at Startup is disabled on all add-on systems.

    • Only the main server should have this setting enabled.

🛑 Step 2: Turn Off Scheduler on Add-On Systems

To avoid conflicts, only the main server should handle automated Scheduler tasks.

Disable Scheduler tasks on add-ons:

  1. Click the Scheduler icon (clock) in the top-right corner of Webgility Desktop.

  2. Choose Review Settings when prompted.

  3. In the Scheduler window, uncheck or disable all scheduled tasks.

  4. Save your changes and close the window.

✅ The Scheduler icon should remain amber (standby) or gray on add-ons, and green (active) only on the main server.

🔐 Step 3: Confirm Connection Permissions Between Systems

If Webgility Desktop add-ons can’t communicate with the main server, automation and order posting will fail.

Check for:

  • Matching server connection info under Settings > Network on each add-on.

  • Proper permissions for the main server to accept incoming connections.

  • Firewall or antivirus blocking Webgility Desktop—if so, add it as an exception.

📦 Step 4: Test Order Posting from an Add-On

After correcting the above settings:

  1. Create or import a test order on a secondary system.

  2. Mark the order as fulfilled or ready to post.

  3. Confirm that the order successfully posts to QuickBooks via the main server.