Moving blogs post with Attachments using Rest API

te_Attachments doesn't have its own index, do you mean that the blog post shows up as indexed?

Have you ensured that Search Index has run since the move?

Are there any exceptions in the exceptions log?

Let me clarify.  The blog post shows up in the old group in the search facet.   It is actually located in the correct group.  However, the duplicate file in te_attachment is still concerning because it is tied to both the old and new blog application with the same contentid.

9109 454 1 0 34207 2482 2012-11-30 14:26:24.770 ESG Offsite Agenda 5 DEC 2012 Rev 4.docx application/vnd.openxmlformats-officedocument.word
27210 836 1 0 34207 0 2021-02-11 19:08:45.670 ESG Offsite Agenda 5 DEC 2012 Rev 4.docx application/vnd.openxmlformats-officedocument.word

Let me clarify.  The blog post shows up in the old group in the search facet.   It is actually located in the correct group.  However, the duplicate file in te_attachment is still concerning because it is tied to both the old and new blog application with the same contentid.

9109 454 1 0 34207 2482 2012-11-30 14:26:24.770 ESG Offsite Agenda 5 DEC 2012 Rev 4.docx application/vnd.openxmlformats-officedocument.word
27210 836 1 0 34207 0 2021-02-11 19:08:45.670 ESG Offsite Agenda 5 DEC 2012 Rev 4.docx application/vnd.openxmlformats-officedocument.word

Can you share the code you are using/endpoints you are calling?

        If Await UpdateTags(dataRow, dataRow("Tags") & String.Format(",Archived From {0}: {1}", dataRow("Group"), dataRow("Application"))) Then
                response = Await host.PostToDynamicAsync(2, "contentconversion/conversion.json", False, New RestPostOptions() With {
                        .AdditionalHeaders = GetHeaders(),
                        .PostParameters = New NameValueCollection() From {
                            {"SourceContentTypeId", dataRow("ContentTypeId")},
                            {"SourceContentId", dataRow("ContentGuid")},
                            {"TargetContentTypeId", dataRow("ContentTypeId")},
                            {"TargetApplicationId", applicationId},
                            {"TargetApplicationTypeId", dataRow("ApplicationTypeId")}
                        }
                    })

What search syntax are you using? just the title/text of the post, or a specific search facet?

specific search facet to return the data I want to move.

Can you share the syntax with the sensitive data removed?

I confirmed that the old attachment record stayed after a move, but after giving search time to update its index, it was showing up properly in the new location for me when searching by title, text, etc.

Is search running properly? Any related exceptions in the logs?

All the moved posts have isindexed=0 in te_blog_posts.  There is nothing wrong with search that I can see and no exceptions show up.  Is the group name correct in the facet in your test? It shows correctly in the results, but the facet filter still has old group name.  This definitely indicates the search is not updating.  

IsIndexed = 0 is definitely indicating the search is not updating. What is the schedule of your Search Indexing job? What's the next scheduled time at Administration > Monitoring > Jobs > filter to "Search Index"?

I logged a bug for the extra attachment record... However, it's not affecting the search indexing issue.

It is Job e112276f-46f9-401d-b763-a1d0e2488280 is scheduled to process at Wed, Aug 25 2021 3:48 PM.

Some of these blogs posts were moved 6 months ago, so the search should have updated by now :-)

Indeed... and there are no exceptions in Administration > Monitoring > Exceptions for the time frame around moving the posts? or any Search Indexing exceptions around/after those times?

Are any of these posts showing the proper updated location when searched?

There are no errors in the logs.  The posts are show correctly in the new blog when searched.  Only issue with that since the search is not updated the facet is incorrect and I can't search by the new tag I applied to the post during the move.  This is only an issue with posts with attachments.  Other posts are fine without attachments are fine