FLX-1021

Generated source 'OrderProcessor.java' was produced from a different model than the one being built

Severity	ERROR
Category	GRAPH_MODEL
Element	NODE

The rule

Checked-in generated source must be regenerated when the graph model changes.

Why the compiler says this

The generated processor carries a digest of the model it was produced from. Recomputing that digest from the current graph gives a different value, so the committed file does not describe this graph. If the build compiled that file before regenerating — which is the usual ordering, since the plugin regenerates at process-classes and compile runs first — any failure it produced points inside generated code and describes yesterday's model, not a defect in your nodes.

How to fix it

Regenerate the processor and commit the result. If the file is meant to be generated rather than committed, remove it from source control and let the build produce it. Stamped 0123456789ab…, current fedcba987654….

Which builds raise it

A verifying step, not generation. During a normal regeneration a differing digest is the expected state, so raising there would fail every legitimate change. Call it from a CI gate, a verifying plugin goal, or before compile in a build that compiles committed generated source.

Reading it programmatically

This diagnostic is also written to the machine-readable report — the opt-in sidecar (-Dfluxtion.diagnostics.sidecar=true), or FluxtionDiagnostics.capture(...) for a caller that wants the objects:

{
  "code": "FLX-1021",
  "severity": "ERROR",
  "category": "GRAPH_MODEL",
  "element": { "kind": "NODE", … }
}

Select findings by severity, never by position: a failing build's report also contains any warnings it found, and diagnostics[0] is not the cause of the failure.

---

This page is generated from the compiler itself, so the wording above is exactly what a build emits. Do not edit it by hand — it is overwritten whenever the diagnostics are regenerated.