Skip to main content
Chris Tammar
Participating Frequently
January 23, 2024
Answered

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

  • January 23, 2024
  • 40 replies
  • 27511 views

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>

Correct answer NOcreationsBE

@Rishabh_Tiwari They originally opened with Chrome. Which did not work. But they just refreshed the link, and it now works. So i think what is happening, is that there's some sort of lag or delay with the file updating, creating an error message. It must be some sort of Adobe server issue. Other's have noticed this too.... The link won't work right away, but when they try again, it works.


I would like to add that my clients usually do not experience any problems opening the file with the link (even if I get the error message), but sometimes they do. Refreshing the page does do the trick in most cases if that happens. Now usually they are 'slow' in reacting on my update messages, so it is possible that they only experience problems opening the file when they react right away. I will keep an eye on that now, to be sure. So I support the idea of a lag/delay in the update process.

40 replies

Participating Frequently
November 19, 2025

It's so incredibly bad that this isn't fixed by Adobe. I use this feature in all my InDesign projects and it creates an incredible amount of more work for me. This is something I pay to have work and it has been messing around on and off for many years. Time to get Adobe to step up and deliver.

Participant
November 18, 2025

I am now getting this error for the first time. Why is this still an issue??

e.e.DeGroot
Participating Frequently
November 13, 2025

Well, it's now 2025 and I'm on version 21.0, Sequoia 15.6.1, and I'm still getting the artifact error. When it used to do this in previous versions, I could usually get it to update at least twice but now it's only letting me do the initial link creation file update. I have to make a whole new file to any any further updates to post, losing my editors' comments. The previous version of INDD was actually fairly stable and I didn't get any errors that I recall over the past several months. It was kind of awesome and my clients were so happy not to have to deal with this!

Thoughts, suggestions?

Participant
November 17, 2025

I am also getting this error! It won't update the link. I have tried restarting, reinstalling the software, trying different documents and its the same thing. Can't update the link. 

Participating Frequently
November 12, 2025

Still getting the error also

Participating Frequently
November 11, 2025

This issue deffinately has not been resolved. Im having this same issue with multiple files still

Participant
November 11, 2025

Can the admins please unmark this issue as solved based on the latest feedback? This seems to be a major bug impacting many users, clearly this is not resolved yet.

J E L
Community Expert
Community Expert
November 11, 2025

Yes, I am still getting the artifact error!

Participant
November 7, 2025

I have this bug for several years now, happening randomly.
Now again in v21.0
Sometimes it even kills the app.
Happens with or without unmapped comments (which happen if the object related to the comment is moved outside the visible board)
I'm trying to guess what happens with the background task panel, and it seems to break at 99%. Not sure why it breaks at that moment.
What would be helpful, before a fix is eventually published, would be to display logs in this background task panel.
At least, we could understand what works, and what breaks in our file...
@Abhishek Rao ?

Participant
October 30, 2025

Getting this issue a lot. I've found if I only have one file open at a time then it doesn't error. Maybe that will help others get around the bug until Adobe gets around to fixing it (seems like its been years and years).

NOcreationsBE
Inspiring
October 30, 2025

@sungkhum don't bother: I hardly ever have more than one document open in InDesign and I get the error anyway. It is quite random, but usually happens only after multiple updates of the Share for Review file and after that the error usually persists.

Participating Frequently
November 4, 2025

I am unable to update the content in Share for Review. It keeps giving me an error message: There was an error updating the artifact.

Also, it says that I last updated 4 days ago. So it is not pushing the updated content to the cloud.

 

I have tried closing the application and restarting. 

 

I am on OS 15.5 and the latest Indesign 2026.

 

Abhishek Rao
Community Manager
Community Manager
October 14, 2025

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
Inspiring
October 14, 2025

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

Abhishek Rao
Community Manager
Community Manager
May 19, 2025

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
Participating Frequently
October 11, 2025

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
Inspiring
October 11, 2025

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??