Hello! When I use the Find Items Shortcuts action in iPadOS, with DTTG 4 installed, I now get consistent failures, whether I confine the search term to a specific group or search all databases. The error is “This operation took too long to complete. Please try again later.” Shortcuts using the Find Items action worked well in the previous DTTG version.
Thank you!
It does not matter whether you constrain the search to a database or group. How complex is your query? And is your data store (all databases on the device) large?
Welcome @jeffpooley and yes, please provide more specific information when reporting issues.
Here is a simple example that works and returns 88 items…
Hello! Ok, great—here are some details:
I have tested with a very simple “name:{{author-lastname}}” search using that Shortcut action, on the smallest database—then it does often work.
With a larger database, or with a more complex query (e.g., NEAR), it almost always fails.
I am able to conduct these searches rapidly on my M1 Mac. I should add that I rarely encountered problems with the Shortcut action in DTTG 3. Manual, in-app search is much, much slower in DTTG 4, as well.
In every other respect, I absolutely adore the update.
I have recorded a brief Loom to demo: [I keep getting errors when I try to add the Loom url]
In addition to the “too long” error, I am also getting an “unknown error” now.
Best, Jeff
I have a similar experience as the OP: Searching for something like name:2026- in “all databases” or a single database gives me an “Operation took to long” message after the light green progress bar seems to have reached its maximum position. The DTTG databases (5) take up about 2GB, 5400 documents.
In DT, this query matches about 40 documents across all databases.
Hmm… I’m doing a name search on all databases, including two with over 10,000 items in each, and it’s returning a result withing a few seconds.
Here: iPad 11 3. Generation, iPadOS 26.3, DTTG 4.0.5
Here, it works if I search with “name:SomeName”, even in all Databases. It fails with “name:2026”. And now I doesn’t even start the search, but immediately tells me that an unknown error occured.
Wild guess: Numbers are treated differently than non-numeric strings? Both search strings work fine in DTTG itself. There’s just something weird going in Shortcuts. What else is new.
Thank you for the observation. However, numbers shouldn’t be treated any differently… We’ll have a look.
