I just return those to be Reindexed.
South Africa Dutch [MQSZ-H1D] is the reference batch.
The ! symbol was mentioned in another topic as meaning a note, see https://community.familysearch.org/en/discussion/comment/538829/#Comment_538829
I do not do indexing but comments I have seen indicate that no one can look at the batch once it is returned
!@#$%^&() are not allowed in indexing. Next time, please hang on to the batch so someone can help you.
Even the Reference images show that (!422). The Image of the Batch does NOT come on. Only a black picture with !422 on the top. Too late. I have already returned them. MQSZ-H1D, H1L, H1H, H1W, CM6. I did see that they were Marriage forms. Only the CM6 I did not see yet.
@Harmon, James Bartlett Hi, still you need to hang on to one batch so that the techies at FS Support can see and do their computer whiz-kid thing ---- it sounds to me like they may have to pull the entire project and re-scan or photo everything 😥
Got one. Batch [MQSZ-H13]. Do I have to call FS Support?
That is ...truly odd.
422 is an HTML error code for "unprocessable entity" or "unprocessable content". It normally implies an error on the user's end: the request couldn't be fulfilled because the server doesn't understand some part or aspect of it. Of course, I have no idea whether FS is using HTML error codes here, but it seems to be the most reasonable assumption.
I will see what I can find out about these.
At least I can see some images in the Reference Image function. -3, -4 and -5
This batch will have to be returned on the 18th. I am still waiting for some help with this.
I have sent it to be reviewed. I will let you know when I hear back. Thanks for reporting the error.
I got a lot more of those. I sent them all back accept one. Just in case. The Help feature didn't help. This is a new issue I guess.
Batch MQSH-JGS This time almost all the reference images are viewable. Only -2 is showing !422. Did a computer with a Virus cause this?
Did a computer with a Virus cause this?
I doubt it. Most viruses are designed to be unobtrusive, because if the user notices a problem, the virus can be caught. (Their goal is to steal information, not just to annoy people.) Causing images to disappear would alert the FamilySearch team that something's wrong.
I think that @Julia Szent-Györgyi's theory is the most likely scenario, especially given that nobody else has chimed in with a similar issue. Have you tried to use a different browser or clear cookies?
I know that is incorrect. ALL of those have been marked as No EX Data. It's NOT my system. By the way, I think they have repaired the issue. The Indexing base took my batches. I think they have been all repaired. A few days ago they gave us a lot of Batches to index and review.
I was told that the issue would be addressed. I am glad that it is working for you @Harmon, James Bartlett