A request to Invantive Data Access Point runs a [[Invantive Data Access Point/Presets|preset]] and returns whatever it produces as one response. Two limits follow from that shape. ## The Preset Must Exist A request naming a preset which is not defined on the server ends with: ``` itgendar068 Please specify an existing preset. ``` The preset named in the `preset` parameter of the request is not present on this Data Access Point server. The remedy lies with whoever administers that server: the preset has to be uploaded there. A preset which works against one server therefore does not work against another until it has been placed there too. ## Size and Duration The whole answer is built before it is sent, so a preset which gathers a great deal of data holds it all at once. A response approaching a gigabyte is where this stops being theoretical: such a request has been seen to run for several minutes and then fail with an arithmetic overflow rather than returning the file. Downloading documents is the usual way to reach that size, because the answer is a ZIP file whose contents are already compressed. Reduce the answer rather than retrying: - narrow the selection, for example by one document category at a time instead of all of them; - narrow by company, by account or by project; - narrow the period. The server logs the size and the duration of every answer it returns, so the message identification of a failed request tells the administrator how large the answer had become before it failed.