Persistent Error in Adobe InDesign: ‘There Was an Error Updating the Artifact

[Chris Tammar]

When I go to update a review link in InDesign, I keep getting this error message "there was an error updating the artifact". After that, the link does not work for most people. I am signed in to Adobe. Everything is up-to-date.... But this issue still persists. Can Adobe please fix this issue? It's emarassing when I go to send the review link to my leaders and they just get an error message when they try opening it.

<Title renamed by moderator>

[NOcreationsBE]

@Abhishek Rao, usually once the error message appears, it keeps reappearing every time in the same document. Sometimes it's more random (then it does for a few times, then it doesn't) and (in my experience) when I save the file with a new name, it can disappear. But then, of course, the review link is also new and the comments are no longer linked, which is not a good workaround. I've been experiencing this for years now with different versions of InDesign, simple and complex files, with resolved, unresolved, mapped and/or unmapped comments, and so it's still totally unclear to me what it could be due to. The only thing I do know, is that  I have never seen the error message appear after uploading a brand new file (the first time you choose Share for review for a file). It only happens after updates.
I understand that this is therefore also difficult for you to reproduce. Possibly the problem is not even related to the file (content or comments) itself. Since many people have this problem, I think it would be more efficient to have many Adobe employees create different files themselves on different devices and share them online for review, so that you can see and test for yourselves on the spot when it occurs and when it does not. That would probably work better than constantly asking complaining users to share files (because you cannot reproduce the issue with these files) and screenshots (because they are always the same) and ask if they have the latest updates (because it's obvious that's not the problem there either).

[Leon1982-2]

Yes, we're all still getting these errors, we're just tired of reporting them. The links typically do work (not always) even when the error is present which took me a long time to figure out. If you do a lot of back and forth edits with clients on a particular document though, you will eventually have to create a new share since it will stop working. This sucks because it erases all of your history. 

[tom_cog]

Also, "It probably updated correctly even though it says it didn't" just doesn't cut it when you're sharing complicated documents for review and final approval.

[NOcreationsBE]

@tom_cog, I completely understand! You can't check 100+ updates in large or complicated documents when you are working with deadlines. The only thing I can tell you, is that I never noticed any changes not updating, even after getting the error. You just have to refresh the page or come back a little later (and refresh the page). It is not a guarantee, but maybe a minor assurance if you have no choice but to work this way and no time to check all upates online.

• I would love to hear from others if they ever experienced that a change in the document was not visible after updating the online version, getting the error message and refreshing the page.

[Abhishek Rao]

Hello everyone,

Thanks for sharing the details. I've escalated this to the product team, and they are currently investigating the issue. I'll keep you posted and share an update as soon as I hear back.

Thanks for your patience. 

Abhishek

[SteveU65]

Seems to me havign experienced this issue on a regular basis and having read the Adobe replies where they test user documents and cannot replicate the error... HAVE they thought of leaving the Adobe building and Intranet and tried testing it as if they were a subscriber and not an Adobe employee - maybe then it might be reproducible?

2020 - 2025 and it still happens to many, many users it is an ADOBE end issue not the users as this period will cover mulititudes of hardware, software versions etc. BUT all into the same Adobe network so the common factor is...

[NOcreationsBE]

Exactly what I was thinking @SteveU65! It happens so often that they say they cannot reproduce the problem/error, also with other issues, while seemingly every user outside Adobe is experiencing the same issue on multiple platforms and multiple versions. How do they work??

[Abhishek Rao]

Hi everyone,

Thanks for your continued patience while we looked into this. I checked with the product team, and they've tested multiple files (including those shared by some of you) but weren’t able to reproduce the issue on their end, even after several tries. It seems to be intermittent, and in many cases, retrying the Update Content option works successfully on subsequent attempts.

The team also noticed in one of the shared recordings that unmapped comments were present, which might be contributing to the error. They're reviewing this further, but for now, please try updating the content again and let us know if it works. If the error persists, kindly check if you notice any unmapped comments and share your observations so we can dig deeper.

Looking forward to your updates.

Abhishek

[NOcreationsBE]

@Abhishek Rao we already established that this error is not related to unmapped comments. See my comment on July 31 2024. 

[Leon1982-2]

Maybe you should have one of us test your software for you? We can replicate the problem consistently/daily. What a dubious response to a continued issue.  Even if the issue were related to unmapped comments (it's not) fix it! There's FIVE pages of copmlaints here... What more do you want us to say?

[Leon1982-2]

Sorry for replying to the wrong person.

[NOcreationsBE]

@Leon1982-2 Apology accepted. It was clear you were not talking to me. 😄

[Good Venture]

Once again, the issue is being shifted onto users instead of being properly addressed. Please stop suggesting that the problem is related to unmapped comments — it isn’t.

Moreover, unmapped comments are themselves a problem, since there should not be any unmapped comments in the first place.

How about Adobe focuses on improving the software to ensure comments don’t become unmapped — if that’s truly the issue?

[Scott28929874pbtb]

I am having the same error as the rest of these users, unmapped comments do not seem to be the issue.