InDesign Share for Review Error

[MelissaM1024]

Hi, I'm trying to use the Share for Review feature and keep getting the error: There was an error creating the artifact. I am using InDesign version 16.2.1 and Windows 10.

Thanks for any help!

[Elliot5CAB]

No still happening

"There was an error creating the artifact."

Happy days

[default21883955a44ijf]

I'm now seeing the same error. Initial generation of review links went smoothly, but now getting a persistent "Error creating the artifact" message. Have tried quitting and re-opening InDesign, making sure the file is saved. 

This is an incredibly disruptive error, and it sounds like it's happening for others as well. 

Our company is paying for Creative Cloud, and the client is paying our company for the work we're doing. Adobe: you're blowing it. Fix this. 

edit: As we proceeded with this project updating the review link we sent the client, it turned out that regardless of the error message, the review link WAS in fact being updated correctly. We checked carefully to see the changes we'd made each time and they were showing up. So, it seems the error message is actually a false alarm, at least in our case. Very disruptive, though! It's no fun to have to abandon a review link with client comments attached -- especially when there isn't an actual problem "creating the artifact" to begin with. 

[LeaAnn33636999mpvs]

I am receiving this error, and I have done everything as outlined in this answer. However, the link does appear to update even with the error. All the changes I have made did, in fact, update on the shared document link. I plan to report it but will continue to use the share feature. It is a much easier way to get feedback. 

[Jeremy@M]

Even worse; inconsistency. Computing 101 suggests that hardware and software are designed to compute consistent processes, algorithms, etc. Adobe has proven time and time again that they get paid to make new features; not making sure the features work as designed.

My experience (along with others) has proven that the share for review feature sometimes WILL update the links even when the error is presented while other times it DOES NOT. This is unacceptable for an enterprise-paid platform.

[Adam283162912qkm]

Happening for me too. Very frustrating considering it seems to have been reported 4 years ago. The whole 'share for review' feature seems buggy and unfinished.

[default21883955a44ijf]

If you don't want to hunt through to verify changes you made were uploaded, you can also view the modification date at your review link. It's in the sidebar on the right, at the "i" icon.

[keithconover]

I have experienced the "spurious error" problem, but right now I have a Share for Review out for comment and the error is not spurious, the changes are not shown in the Share for Review.

I do not regard this issue as solved.

Uwe suggested it was a problem with a pre-existing file in the caches folder. On my Windows 11 system, this is: C:\Users\kcono\AppData\Local\Adobe\InDesign\Version 19.0\en_US\Caches\Artifact. I tried closing InDesign, deleting everything in that folder, and trying again.

I can export my document to PDF (Print) with an PDF/X-4 preset without any error.

This is my computer information:

This is Task Manager after my computer is freshly rebooted:

This is Task Manager after rebooting and then starting InDesign with no file open:

This is after I open the file in question in InDesign:

Uwe suggested this might a problem with the cache folder. On my Windows 11 system, this is

C:\Users\kcono\AppData\Local\Adobe\InDesign\Version 19.0\en_US\Caches\Artifact:

I tried moving everything in this folder to a subfolder (temp) and then updating the Share for Review. Got the same error, and this is what the cache folder looked like:

The Share for Review was again not updated online.

Given all the issues I've had with Share for Review, if I can't get this fixed in a week, I'm going to  abandon it and badmouth it to everyone I can get to listen. Share for Review has such potential, but Adobe docsn't seem to be able to get it to where it works reliably. I did try to provide as much detail as I could, in the hopes that Adobe might be able to use this information to fix it. I certainly have failed.