- Issue created by @capysara
- Merge request !68#3471261 – Update error log message for integration link removal → (Open) created by capysara
- Issue was unassigned.
- Status changed to Needs review
11 months ago 3:28pm 30 August 2024 - 🇺🇸United States capysara
Created a MR to update the log error to be more helpful. I need to do some more research because this issue might part of a larger problem or might be specific to my site, but the error message is a positive step regardless.
- Status changed to Needs work
9 months ago 2:36pm 5 November 2024 - 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
MRs of bugfixes should target the
1.0.x
branch. - Merge request !84#3471261 – Update error log message for integration link removal → (Merged) created by capysara
- 🇺🇸United States capysara
capysara → changed the visibility of the branch asset-id-missing-integration-link-3471261 to hidden.
- 🇺🇸United States capysara
capysara → changed the visibility of the branch 3471261-missing-integration-links to hidden.
- First commit to issue fork.
-
japerry →
committed cdb8d840 on 1.0.x authored by
capysara →
#3471261 – Update error log message for integration link removal
-
japerry →
committed cdb8d840 on 1.0.x authored by
capysara →
-
japerry →
committed 23187da2 on 1.1.x authored by
capysara →
#3471261 – Update error log message for integration link removal
-
japerry →
committed 23187da2 on 1.1.x authored by
capysara →
- 🇭🇺Hungary Balu Ertl Budapest 🇪🇺
On Acquia's internal channels, we have received reports of very similar errors to happen. Based on the formatting of error messages I see on Watchdog screenshots, I can tell that the Customer was using a version of this module before the MR !84 was merged.
Although handling of HTTP 4xx errors from asset-related API requests has been improved in the 1.1.x branch, but it is uncertain whether it covers integration link-related requests too or not. Independently from HTTP 4xx errors, I do agree with @capysara → 's suspicion about if the CRUD operations of integration links are not in full sync with the DAM assets during their entire lifecycle. As the auto-hiding logic instantly sets media items unpublished at any time when the Widen API returns a response with negative meaning (aka. asset unavailable or deleted), these are not permanent changes on Widen's side (asset can be available later on and even can be restored from trashbin by admin). Therefore we don't delete media items automatically, so – up to my current understanding – we should not delete integration links either.
For the sake of transparency (and because we have referenced this ticket earlier from various sources) I restored its original issue description which was clearly about solving the link deletion problems. Also, bumping branch up to
1.1.x
because it could be easier due to the aforementioned feature already implemented there. - Status changed to Closed: works as designed
10 days ago 6:30am 25 July 2025 - 🇮🇳India rajeshreeputra Pune
Tested with 1.1.x - the integration link registration now completes successfully without throwing errors. When assets are deleted from Acquia DAM, the system now removes the corresponding queue entries instead of keeping it in queue and throwing the error.