docs: document the project node limitations - #8071
Open
dimitrieh wants to merge 1 commit into
Open
Conversation
The page presents calling a shared instance's flows as the headline use case without stating that only hosted instances can be addressed directly, that a remote instance can send but never receive, or that a call waits 30 seconds for a target that has to be running. Also fixes a typo and the implication that remote instances are symmetric peers.
Contributor
Author
|
Small fix, based on research done into link nodes resuling in that we can better inform users of link nodes needing logic to reside on hosted instances Slack thread: https://flowfuse.slack.com/archives/C03FAUBPPJ7/p1785930859746159?thread_ts=1785861957.912329&cid=C03FAUBPPJ7 |
hardillb
approved these changes
Aug 6, 2026
sumitshinde-84
approved these changes
Aug 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The page presents calling a shared instance's flows as the headline use case for these nodes, but states none of the constraints a builder hits.
Adds a Limitations section covering:
Project Innode, and travels through the broker, so it is unavailable to a caller that is offlineAlso fixes "links to extended" and the implication that remote instances are symmetric peers.
Paired with FlowFuse/nr-project-nodes#255, which puts the same facts in the node help and the error messages.