Invantive Bridge Online applies daily limits per subscription, so that one heavy download does not spoil the response times for everyone else on the service. ## What Is Counted Four measures are tracked: - the volume of data exchanged; - the number of requests made; - the total time the requests took; - the number of rows retrieved from a table. Each is counted twice: once for fresh data, which had to be fetched from the platform, and once for all data, which includes what came from the cache. The distinction matters because a repeated download served from the cache costs the platform nothing while it still costs the service something. ## Staying Within Them Consumption is visible on the Bridge Online dashboard, and every response carries HTTP headers with the same figures, so a client can track its own use without opening the dashboard. Where a download runs into the limits, the remedy is nearly always to retrieve less rather than to retrieve again: - select only the columns actually used, instead of every column of a table; - filter at the source, so the platform sends fewer rows; - schedule fewer full downloads and rely on the cache in between; - avoid running several downloads in parallel against the same platform, which divides the available speed over them and makes each one count longer against the duration. ## Slow Platforms The duration limits were set to bound processing time, but a platform which answers slowly consumes duration without consuming much of anything else. Teamleader Focus is the known example: retrieving custom field values costs many single-record requests against an API with a low speed limit, so downloads there meet the duration limit sooner than the volume would suggest. Where a platform is the bottleneck rather than the volume, retrieving less of it is still the only lever on this side.