Failed to update fields correctly on document change and Re-deployment

[sulavsssmc]

There could be an issue in "Re-deploy" function.

The deploy hook is set to "Live Updates"
I had a total of 2213 documents in a collection. Some were "published" and some status were "modified".
When i deployed for the first time on a new index, only 2198 documents were uploaded. I did not select "Include draft" function.
Then i realised that maybe some issue is coming because not all documents are at published state.
So i bulk published all 2213 documents, 100 at a time from strapi collection table.
I was getting a message on Orama cloud that data set has been modified and was prompting be to "re-deploy" the index"

There is redeploy button on Strapi's orama cloud dashboard, so i tried using that but no luck. and on projects's console i could see:
[2025-02-05 18:48:47.077] error: Collection not valid.
[2025-02-05 18:48:47.077] http: POST /orama-cloud/collections/pdtsggthahtfo3jmveiqz0xr/deploy (54 ms) 204

Currently the status of index is shown as "Updated" and last run was shown as "7 hours ago"

Then i manually clicked the "re-deploy" on Orama Cloud Dashboard (Not the one on strapi)
Then it started deploying and it showed only 2113 documents and said 15 upserts and 100 deletions.
However when i tested the search, the "title" field was still empty like it used to be in the draft state but after deploying the title should have been updated with the data which is at published state.

Steps to reproduce problem:

1. create a document in a collection.
2. fill some fields and save it. (don't publish). and it will show that it is at "modified" state.
3. Now deploy all documents as "modified" state to the Orama
4. publish them and status will be set to "Published"
5. Now try to re-deploy them from strapi dashboard and it won't work. (Problem 1)
6. Manually re-deploy from Orama Cloud official dashboard
7. The changes in published documents should reflect in the Orama cloud but it will still have the old "Modified" state data. (Problem 2)

Expected outcome:
If i change the status of the document from "modified" to "published", then that change should be reflected on orama cloud. I don't know whether the id of modified and published are same or not. which is why in previous issue i had highlighted that strapi has implemented "documentId" as a common unique id shared between published and draft or modified document (idk whether this and draft are same).

If i click on re-deploy, it should re-deploy on Orama Cloud. Currently i had to manually login to orama cloud and re-deploy from there.

Please let me know if i need to share other info on this.