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

Resolving Slow Performance and Connection Failures in Webgility Desktop Extension

This article helps Webgility Online users in diagnosing and resolving persistent connection problems and slow performance when integrating the Webgility Desktop Extension with QuickBooks Desktop. It offers detailed troubleshooting steps to improve connectivity and optimize performance, ensuring a stable and efficient accounting integration experience.

Overview

This guide provides detailed steps for diagnosing and resolving persistent connection problems and slow performance when integrating the Webgility Desktop Extension (WDE) with QuickBooks Desktop (QBD) for accounting purposes.

Common Issues

  • Intermittent or persistent disconnections between Webgility Online and QBD
  • Slow sync or integration processes after resetting connections
  • User reports of waiting or timeouts during integration

Step-by-Step Resolution

1. Verify Reported Symptoms

  • Gather full error messages and timestamps.
  • Confirm if slowness is ongoing or temporary.
  • Check for recent changes to QBD/Webgility environments.

2. Reset Client Configuration

  • Perform a reset of the client configuration via Webgility Extension Settings.
  • Reinstall the Webgility extension from the Webgility portal.
  • Save and close configuration settings.

3. Reconnect Webgility Desktop Extension to QBD

  • Launch Webgility Desktop Extension.
  • Navigate to Connections > QuickBooks Desktop.
  • Follow the guided authentication workflow:
    • Enter QBD admin credentials if prompted.
    • Authorize access when requested.
  • Validate that a successful connection is displayed in the Webgility UI.

4. Monitor Performance

  • After reconnecting, try to perform basic sync operations (e.g., download a test batch of transactions).
  • Use Webgility and Windows Task Manager to observe CPU, memory, and network usage on the client machine.
  • Note any spikes or persistently high usage that corresponds with performance delays.