I’m attempting to replicate our GL entries into CosmosDB. The original job you can see in the attached image resulted in ~80% of the GL entries being replicated, however, the number of records in CosmosDB remains static while the job still is in “Started” status. It appears as if the original replication job is hung and any subsequent attempt to restart the sync fail (albeit after quite some time).
My first thought was to cancel the original job so a new job could start fresh, but it doesn’t appear we have the option to cancel a job.
Any suggestions?
The job is probably timed out.
You can schedule a manual replication of missing records in the “Replication Todo List” window.
Enter a random Engine ID, and they specify either an entry number range or set a set of filters. You can set multiple jobs (to reduce the change of a replication job getting killed by Microsoft updates)