Instance Data Replication - Seeding is not getting started and stuck in QUEUED stateIssue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } The replication sets in producer and consumer instances are created and the replication status show ACTIVE replication. But the seeding request is stuck in QUEUED state in consumer instance for both partial and full seeding requests. Below steps followed to verify the seeding is still stuck: -Monitor the records in below table "idr_seeding_request" displays the state not completed. -Recreate the replication set from scratch after canceling the current stucked seeing request -Check if a consumer replication set is listed avaliable in IDR diagnostics page on the producer instance.https://instancexxxx.service-now.com/now/nav/ui/classic/params/target/idr_diagnostics.do Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Xanadu Patch 1 Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } -Check if the idr topic is created in the consumer instance and validate the workaround below KB which is a PRB1897813:https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB2287977//Scriptvar metadataTopicToRecreate = 'idr.a36821a56ffc6900ffcca9cc5d3ee486.da4027754fc392007b9b220f0310c7a4';var hermesService = 'hermes-internal';new Packages.com.glide.hermes.demo.TopicManagerDemo().deleteTopic(metadataTopicToRecreate, true, hermesService);new Packages.com.glide.hermes.demo.TopicManagerDemo().createTopic(metadataTopicToRecreate, 1 , true, hermesService);new Packages.com.glide.hermes.demo.TopicManagerDemo().invalidateMetadataCache();-Check hermes_cluster_config table on both insances if it lists the records pointing out to corresponding instance. If you are checking the consumer instance, please check if this table has a record for producer instance in hermes_cluster_config table.-Check if IDRSeedingProducerJob is active in sysauto table. -Check if the IDRSeedingProducerJob has an associated record in sys_trigger table. If not , please reactivate the IDRSeedingProducerJob job to automatically create the record in sys_trigger table.