The seeded Hydra Triage graph (lib/Repair/SeedHydraTriageFlow.php) has a command stop node whose message reads:
A label was proposed and recorded. No forge write was attempted: the OpenConnector-backed command node is not installed on this instance.
That is no longer true. GET /apps/openregister/api/flow/node-catalog on this instance returns 13 registered node types including openconnector.source-call and openconnector.synchronization-run (openconnector 0.3.3, files present in the container, registration gated only by a class_exists() guard on the event class which passes).
Why it matters: the message is the first thing anyone debugging the graph will read, and it points at the wrong cause. The actual blocker is credential scope — openconnector.source-call needs a Source, and a brokered GitHub Source needs a credential whose allowed_apps includes openconnector. Both brokered github credentials are scoped ["hermiq"], so the flow engine cannot make a forge call regardless of which nodes are registered.
I hit that credential blocker independently from the other direction before finding this graph; the two corroborate.
Suggested fix: replace the stop node with the real openconnector.source-call command step, or — if that is premature — reword the message to name the credential scope rather than a missing node. A stale explanation in a stop message is worse than none, because it reads as a diagnosis.
Context: hydra#421, hydra#419.
The seeded
Hydra Triagegraph (lib/Repair/SeedHydraTriageFlow.php) has acommandstop node whose message reads:That is no longer true.
GET /apps/openregister/api/flow/node-catalogon this instance returns 13 registered node types includingopenconnector.source-callandopenconnector.synchronization-run(openconnector 0.3.3, files present in the container, registration gated only by aclass_exists()guard on the event class which passes).Why it matters: the message is the first thing anyone debugging the graph will read, and it points at the wrong cause. The actual blocker is credential scope —
openconnector.source-callneeds a Source, and a brokered GitHub Source needs a credential whoseallowed_appsincludesopenconnector. Both brokeredgithubcredentials are scoped["hermiq"], so the flow engine cannot make a forge call regardless of which nodes are registered.I hit that credential blocker independently from the other direction before finding this graph; the two corroborate.
Suggested fix: replace the stop node with the real
openconnector.source-callcommand step, or — if that is premature — reword the message to name the credential scope rather than a missing node. A stale explanation in a stop message is worse than none, because it reads as a diagnosis.Context: hydra#421, hydra#419.