#14467·gocd

Pipeline Not Triggered Due to Material Update Failure Caused by Flyweight Corruption

Author: SoaadMahmoudCreated Jul 2, 2026Updated Jul 2, 2026
Labelsmaterialsartifactsquestion

Summary

We are currently facing an issue with material updates, and the following error continues to occur even though the token is valid and no changes have been made on the GoCD server side. It appears that the flyweight directory is becoming corrupted, which is causing the problem. We need to identify the root cause and implement a permanent fix.

the error is Messages Errors Modification check failed for material: URL: https://githubURL, Branch: main Affected pipelines are test1,test2. Error performing command: --- Command --- git config remote.origin.url --- Environment --- {} --- INPUT ---- --- EXIT CODE (1) --- --- STANDARD OUT --- --- STANDARD ERR --- ---

Environment

Basic Details:

  • Go Server Version: 23.2.0
  • JVM Version: 17.0.8
  • OS Information: redhat8

Additional Details (if relevant):

  • Browser vendor/version: edge/ chrome
  • Relevant plugins in use: yaml

Deployment mechanism (e.g. static vs elastic, Docker, Kubernetes, RPM package etc)

  • Go Server: installed rpm in linux environment
  • Go Agent(s): containerized

Support Environment

json

Steps to Reproduce

materials updates suddenly failed to update with below error Error performing command: --- Command --- git config remote.origin.url --- Environment --- {} --- INPUT ---- --- EXIT CODE (1) --- --- STANDARD OUT --- --- STANDARD ERR --- ---

Actual Results

Error performing command: --- Command --- git config remote.origin.url --- Environment --- {} --- INPUT ---- --- EXIT CODE (1) --- --- STANDARD OUT --- --- STANDARD ERR --- ---

Expected Results

can retrieve commit from github

Log snippets

<paste relevant log snippets here>

Possible Fix

No response

Any other info

No response