POST /end-users/{id}/passthrough/{integrationSlug}), Conductor will wait up to 4 minutes by default.
If you prefer a different timeout period, you can customize it by setting the
Conductor-Timeout-Seconds request header to your desired value.-
Large Data Requests: Without paginating your requests (via the
MaxReturnedor other range-based parameters), you may unintentionally request tens of thousands of records in a single call. Processing such a large volume of data can take several minutes in QuickBooks Desktop. - Sequential Processing: QuickBooks Desktop can only process one request at a time. If multiple requests are sent concurrently, they are placed in a queue and processed sequentially, requiring sufficient time for each request to complete before the next one can begin. When several company files share one computer, the Web Connector also works on one company file at a time, so requests for different company files wait for each other too, and each switch to another company file takes 20 to 40 seconds while QuickBooks Desktop opens it.
- Potential Program Startup: If QuickBooks Desktop is not open but the user’s computer is on, online, signed in to the Windows user that runs the Web Connector, and the Web Connector is running in the background, Conductor will automatically launch QuickBooks Desktop when a request is made. Given that QuickBooks Desktop can take at least 30 seconds to start, this can add considerably to the response time.
If the Web Connector has not checked in within the request’s timeout period
when you send the request, for example because it is not running, Conductor
immediately returns an
INTEGRATION_CONNECTION_NOT_ACTIVE error without
initiating the timeout period.
