When running cron the first time after install we get the following error:
Failed to fetch asset ids: Client error: `GET https://api.widencollective.com/v2/assets/search?limit=100&offset=10000&query=lastEditDate%3A%5Bafter%201969-12-31T17%3A00%3A00Z%5D%20AND%20rd%3A%28%5Bbefore%2008%2F11%2F2022%5D%20OR%20%5B08%2F11%2F2022%5D%29%20AND%20ed%3A%28%28isEmpty%29%20OR%20%5Bafter%2008%2F11%2F2022%5D%29&include_deleted=true&include_archived=true` resulted in a `400 Bad Request` response:
{
"error": true,
"response_code": 400,
"error_message": "Sum of limit and offset must not exceed 10,000.",
"stac (truncated...)
Causes For Concern
What impact does this have on accounts with more than 10,000 assets?
Can this happen other times than first cron run and what would be the consiquences?
Steps to Reproduce
1. Install module
2. Connect to DAM account with more than 10,000 assets
3. Run cron
Comments
Comment #2
damondt commentedComment #3
damondt commentedComment #4
damondt commentedComment #5
japerryMoving to the Acquia DAM queue as I'm guessing its still an issue? If not I'd suggest upgrading (if you haven't already)
Comment #6
vipin.mittal18Comment #7
manojapare commentedIssue is reproduce able by clicking on Last in pagination of Media Library form field widget.

Screenshots:
1. Before clicking the Last pagination link (Hided the actual image assets from the screenshot)
2. After clicking the Last pagination link
Comment #8
vipin.mittal18Thanks @manojapare, we are actively implementing the necessary fixes, and you can expect a prompt resolution to this concern.
Comment #11
ankitv18 commentedAdded a minor suggestion to shorter warning message, rest looks good and resolve the problem.
Patch: https://git.drupalcode.org/project/acquia_dam/-/merge_requests/103.patch (Use this patch for now)
Comment #12
vipin.mittal18Comment #13
ankitv18 commentedThats how the warning message looks like ~~ included the patch to validate on local

Comment #15
rajeshreeputraFor some reason, this issue remains in the review state. However, I am marking it as fixed.sorry wrong comment.
Comment #17
rajeshreeputraComment #19
amangrover90 commented