Conifg repo error

[ashok reddy C k]

Hi Team,

We are experiencing an issue with the new code changes in the config repositories. Although these updates have been applied,
we are receiving an error after some time. How can we resolve this issue?

I haven’t seen any logs (go-server.log )either, and we are facing this problem across all config repositories.

There was an error parsing this configuration repository:INVALID MERGED CONFIGURATION Number of errors: 1+ 1. Duplicate artifacts defined

[Chad Wilson]

Not sure if there is a bug that got you into this state, and the error does not seem to be very helpful as it's not telling you the problematic pipeline/job, but it means that within a pipeline's job somewhere, there are two artifact configurations within the same job that have identical `src` and `dest` as each another.

It's the equivalent of this type of error from the UI:




First I'd check through the pipelines in your config repos for any duplicates.

If the config repo defined pipelines look OK, perhaps look at the server config.xml, search for <artifacts> and see if somehow a pipeline with a duplicate has got into the "master" configuration for any manually defined pipelines which is preventing config repo pipelines from being reflected. If so, use the config XML editor, or the UI to correct that pipeline definition. Technically this shouldn't be possible, but perhaps there has been some edge case bug where it is possible to get the config into a non-validated state. I'd expect you to see logs in go-server.log if this is the case, so it's more likely that one of your config repos is the problem.

Once you figure out the problem, if you can share what the issue was (where was the bad config?), we can probably improve the error message to make it easier to find and fix in future.

-Chad

[ashok reddy C k]

Yes, you are right. We have found that two pipelines have the same job. Let me ask my dev team to delete those jobs.


Thanks @Chad Wilson 

--
You received this message because you are subscribed to the Google Groups "GoCD Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+un...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/go-cd/CAEe7TBzK4XKXvXJ2rZcXoeTxQaSwsQE8XQd%2BeWF9gU3e748acw%40mail.gmail.com.

[ashok reddy C k]

we have deleted duplicate artifacts,

But still showing below  error

There was an error parsing this configuration repository:INVALID MERGED CONFIGURATION Number of errors: 1+ 1. Duplicate artifacts defined. - For Config Repo: ssh://g...@git.abcd.xyz:7999/skyspcop/webhooktest.git at revision adb862d1647e85b8ce0ef8b50fab0f603c47c012 Logs:
2026-04-16 08:14:24,407 ERROR [125@MessageListener for ScheduleCheckListener] BuildCauseProducerService:221 - Error while scheduling pipeline: EPAP-ARTIFACT-DEPLOYMENT-UAT
com.thoughtworks.go.server.service.dd.MaxBackTrackLimitReachedException: Maximum Backtracking limit reached while trying to resolve revisions for material DependencyMaterialConfig{pipelineName='EPAP-SESSION-TOKEN-SERVICE', stageName='Get_Session_Token'}
        at com.thoughtworks.go.server.service.dd.DependencyFanInNode.hasMoreInstances(DependencyFanInNode.java:233)
        at com.thoughtworks.go.server.service.dd.DependencyFanInNode.fillNextRevisions(DependencyFanInNode.java:128)
        at com.thoughtworks.go.server.service.dd.DependencyFanInNode.setRevisionTo(DependencyFanInNode.java:95)
        at com.thoughtworks.go.server.service.dd.FanInGraph.iterateAndMakeAllUniqueScmRevisionsForChildrenSame(FanInGraph.java:294)
        at com.thoughtworks.go.server.service.dd.FanInGraph.computeRevisions(FanInGraph.java:180)
        at com.thoughtworks.go.server.service.PipelineService.getRevisionsBasedOnDependencies(PipelineService.java:210)
        at com.thoughtworks.go.server.service.AutoBuild.fanInOn(AutoBuild.java:108)
        at com.thoughtworks.go.server.service.AutoBuild.onModifications(AutoBuild.java:67)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.newProduceBuildCause(BuildCauseProducerService.java:192)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.newProduceBuildCause(BuildCauseProducerService.java:149)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.autoSchedulePipeline(BuildCauseProducerService.java:111)
        at com.thoughtworks.go.server.scheduling.ScheduleCheckListener.onMessage(ScheduleCheckListener.java:44)
        at com.thoughtworks.go.server.scheduling.ScheduleCheckListener.onMessage(ScheduleCheckListener.java:24)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:85)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:64)
        at java.base/java.lang.Thread.run(Thread.java:840)
2026-04-16 08:14:24,446 ERROR [120@MessageListener for ScheduleCheckListener] BuildCauseProducerService:217 - No modifications found for CDP_UI_VERACODE_SCAN_QA_NEW/972/RunVeracodeScan/1. Material Database Update for this instance has not completed.
com.thoughtworks.go.server.service.NoModificationsPresentForDependentMaterialException: No modifications found for CDP_UI_VERACODE_SCAN_QA_NEW/972/RunVeracodeScan/1. Material Database Update for this instance has not completed.
        at com.thoughtworks.go.server.service.dd.FanInGraph.createFinalRevisionsForDepChildren(FanInGraph.java:224)
        at com.thoughtworks.go.server.service.dd.FanInGraph.computeRevisions(FanInGraph.java:184)
        at com.thoughtworks.go.server.service.PipelineService.getRevisionsBasedOnDependencies(PipelineService.java:210)
        at com.thoughtworks.go.server.service.AutoBuild.fanInOn(AutoBuild.java:108)
        at com.thoughtworks.go.server.service.AutoBuild.onModifications(AutoBuild.java:67)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.newProduceBuildCause(BuildCauseProducerService.java:192)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.newProduceBuildCause(BuildCauseProducerService.java:149)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.autoSchedulePipeline(BuildCauseProducerService.java:111)
        at com.thoughtworks.go.server.scheduling.ScheduleCheckListener.onMessage(ScheduleCheckListener.java:44)
        at com.thoughtworks.go.server.scheduling.ScheduleCheckListener.onMessage(ScheduleCheckListener.java:24)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:85)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:64)
        at java.base/java.lang.Thread.run(Thread.java:840)
2026-04-16 08:14:24,458 WARN  [120@MessageListener for ScheduleCheckListener] BuildCauseProducerService:176 - Error while scheduling pipeline: Q3UNIT-RealtimeApp-QA. Possible Reasons: (1) Upstream pipelines have not been built yet. (2) Materials do not match between configuration and build-cause.
2026-04-16 08:14:24,461 WARN  [119@MessageListener for ScheduleCheckListener] DependencyFanInNode:195 - [Fan-in] - Incompatible materials for CDP-Interactive-Insights-Notebook-Hotfix/18/PublishNexusArtifact/1.Config: [66429d9204cbcbe19a8f21e5a4df47f57ec2959e66e151b1433d0821d4eea660]. Instance: [].
2026-04-16 08:14:24,485 WARN  [119@MessageListener for ScheduleCheckListener] DependencyFanInNode:195 - [Fan-in] - Incompatible materials for DCDP_UI_PreProd_Gate/3/Manual_Gate/1. Config: [1295b03ce98fb3dadc205b22fe5e3fee485b5084326e422dd3aaf33f86c4c377]. Instance: [].
2026-04-16 08:14:34,351 WARN  [116@MessageListener for ScheduleCheckListener] DependencyFanInNode:195 - [Fan-in] - Incompatible materials for supernova-playwright-dev-model-order2/111/Test/1. Config: [565727584d9a05977179e4d5e3c5d2c775f34137978c61eec02686f5f9cdce4f]. Instance: [].
2026-04-16 08:14:34,364 WARN  [117@MessageListener for ScheduleCheckListener] DependencyFanInNode:195 - [Fan-in] - Incompatible materials for Prospect-AWS-Create-Databricks-jobs-VSM/7/create-databricks-jobs/1.Config: [7646216e1afa0692adeb662ae1660c4e1acbb7adfd06f3f313721e32abaabcbe]. Instance: [].
2026-04-16 08:14:34,387 WARN  [118@MessageListener for ScheduleCheckListener] DependencyFanInNode:195 - [Fan-in] - Incompatible materials for supernova-playwright-qa-model-order2/43/Test/1. Config: [44a45abc44d3a05a486b2ce20707523d86bdf3aa5b467964486f773b98d18889]. Instance: [].
2026-04-16 08:14:34,424 ERROR [123@MessageListener for ScheduleCheckListener] BuildCauseProducerService:221 - Error while scheduling pipeline: EPAP-ARTIFACT-DEPLOYMENT-UAT
com.thoughtworks.go.server.service.dd.MaxBackTrackLimitReachedException: Maximum Backtracking limit reached while trying to resolve revisions for material DependencyMaterialConfig{pipelineName='EPAP-SESSION-TOKEN-SERVICE', stageName='Get_Session_Token'}
        at com.thoughtworks.go.server.service.dd.DependencyFanInNode.hasMoreInstances(DependencyFanInNode.java:233)
        at com.thoughtworks.go.server.service.dd.DependencyFanInNode.fillNextRevisions(DependencyFanInNode.java:128)
        at com.thoughtworks.go.server.service.dd.DependencyFanInNode.setRevisionTo(DependencyFanInNode.java:95)
        at com.thoughtworks.go.server.service.dd.FanInGraph.iterateAndMakeAllUniqueScmRevisionsForChildrenSame(FanInGraph.java:294)
        at com.thoughtworks.go.server.service.dd.FanInGraph.computeRevisions(FanInGraph.java:180)
        at com.thoughtworks.go.server.service.PipelineService.getRevisionsBasedOnDependencies(PipelineService.java:210)
        at com.thoughtworks.go.server.service.AutoBuild.fanInOn(AutoBuild.java:108)
        at com.thoughtworks.go.server.service.AutoBuild.onModifications(AutoBuild.java:67)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.newProduceBuildCause(BuildCauseProducerService.java:192)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.newProduceBuildCause(BuildCauseProducerService.java:149)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.autoSchedulePipeline(BuildCauseProducerService.java:111)
        at com.thoughtworks.go.server.scheduling.ScheduleCheckListener.onMessage(ScheduleCheckListener.java:44)
        at com.thoughtworks.go.server.scheduling.ScheduleCheckListener.onMessage(ScheduleCheckListener.java:24)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:85)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:64)
        at java.base/java.lang.Thread.run(Thread.java:840)
2026-04-16 08:14:34,455 ERROR [122@MessageListener for ScheduleCheckListener] BuildCauseProducerService:217 - No modifications found for CDP_UI_VERACODE_SCAN_QA_NEW/972/RunVeracodeScan/1. Material Database Update for this instance has not completed.
com.thoughtworks.go.server.service.NoModificationsPresentForDependentMaterialException: No modifications found for CDP_UI_VERACODE_SCAN_QA_NEW/972/RunVeracodeScan/1. Material Database Update for this instance has not completed.
        at com.thoughtworks.go.server.service.dd.FanInGraph.createFinalRevisionsForDepChildren(FanInGraph.java:224)
        at com.thoughtworks.go.server.service.dd.FanInGraph.computeRevisions(FanInGraph.java:184)
        at com.thoughtworks.go.server.service.PipelineService.getRevisionsBasedOnDependencies(PipelineService.java:210)
        at com.thoughtworks.go.server.service.AutoBuild.fanInOn(AutoBuild.java:108)
        at com.thoughtworks.go.server.service.AutoBuild.onModifications(AutoBuild.java:67)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.newProduceBuildCause(BuildCauseProducerService.java:192)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.newProduceBuildCause(BuildCauseProducerService.java:149)
        at com.thoughtworks.go.server.scheduling.BuildCauseProducerService.autoSchedulePipeline(BuildCauseProducerService.java:111)
        at com.thoughtworks.go.server.scheduling.ScheduleCheckListener.onMessage(ScheduleCheckListener.java:44)
        at com.thoughtworks.go.server.scheduling.ScheduleCheckListener.onMessage(ScheduleCheckListener.java:24)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:85)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:64)
        at java.base/java.lang.Thread.run(Thread.java:840)


and 

2) 2026-04-16 10:24:32,674 WARN  [127@MessageListener for ConfigMaterialUpdateListener] GoFileConfigDataSource:347 - Merged config update operation failed on LATEST 103 partials. Falling back to using LAST VALID 102 partials. Exception message was: Number of errors: 1+

1. Duplicate artifacts defined.

com.thoughtworks.go.config.exceptions.GoConfigInvalidMergeException: Number of errors: 1+
1. Duplicate artifacts defined.

        at com.thoughtworks.go.config.MagicalGoConfigXmlLoader.validateCruiseConfig(MagicalGoConfigXmlLoader.java:130)
        at com.thoughtworks.go.config.MagicalGoConfigXmlLoader.preprocessAndValidate(MagicalGoConfigXmlLoader.java:118)
        at com.thoughtworks.go.config.MagicalGoConfigXmlWriter.write(MagicalGoConfigXmlWriter.java:70)
        at com.thoughtworks.go.config.GoFileConfigDataSource.configAsXml(GoFileConfigDataSource.java:406)
        at com.thoughtworks.go.config.GoFileConfigDataSource.getUnmergedConfig(GoFileConfigDataSource.java:592)
        at com.thoughtworks.go.config.GoFileConfigDataSource.trySavingConfig(GoFileConfigDataSource.java:576)
        at com.thoughtworks.go.config.GoFileConfigDataSource.writeWithLock(GoFileConfigDataSource.java:341)
        at com.thoughtworks.go.config.CachedGoConfig.writeWithLock(CachedGoConfig.java:152)
        at com.thoughtworks.go.config.GoConfigDao.updateConfig(GoConfigDao.java:117)
        at com.thoughtworks.go.server.service.GoConfigService.updateConfig(GoConfigService.java:275)
        at com.thoughtworks.go.config.PartialConfigService.updateConfig(PartialConfigService.java:159)
        at com.thoughtworks.go.config.PartialConfigService.onSuccessPartialConfig(PartialConfigService.java:87)
        at com.thoughtworks.go.config.GoConfigRepoConfigDataSource.notifySuccessListeners(GoConfigRepoConfigDataSource.java:209)
        at com.thoughtworks.go.config.GoConfigRepoConfigDataSource.onCheckoutComplete(GoConfigRepoConfigDataSource.java:172)
        at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.updateConfigurationFromCheckout(ConfigMaterialUpdateListener.java:98)
        at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.onMessage(ConfigMaterialUpdateListener.java:83)
        at com.thoughtworks.go.server.materials.ConfigMaterialUpdateListener.onMessage(ConfigMaterialUpdateListener.java:36)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.runImpl(JMSMessageListenerAdapter.java:85)
        at com.thoughtworks.go.server.messaging.activemq.JMSMessageListenerAdapter.run(JMSMessageListenerAdapter.java:64)
        at java.base/java.lang.Thread.run(Thread.java:840)

Note: EPAP*
D1EPAP*
S1EPAP*

all pipeline duplicate artifacts we have dleeted 

but still facing issue

INVALID MERGED CONFIGURATION Number of errors: 1+ 1. Duplicate artifacts defined.

[Jason Smyth]

Hello Ashok,

Except for the last one, the log messages from your post have nothing to do with the invalid configuration. The last one just repeats the same error you see in the UI.

In my experience, while the error messages may obscure important details, they do not lie. If error message states that there are still duplicate artifacts, there are likely still duplicate artifacts.

Since this error likely originates in the code stored in your config repos, there is nothing we can really help you with. Since you're using Git, you might want to consider rolling back to a known good state via git checkout -> git commit.

Good luck,

Jason