You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We're experiencing issues with Project nodes again.
When sending messages through a Project Request node, everything works fine up until, at some time, return messages are not being sent back.
The flow the message is being sent to keeps working, only the return (from a Project Out - Return) is not processed properly, or at all.
We can remedy the problem by changing the time-out of the Project node and redeploying. After that action the flow return works as expected (and the flow returns a message well with the time-out period, like 4s where time-out is 60s). It appears the Project node settings need to be altered, just restarting the flows (Full Deploy) appears to not make a difference.
Currently, we're setting up a Catch trigger so we get notified when a Project node times out. We see this happening but at the moment we have no idea how often this is happening.
PS:
This issue is very much similar to the issue we encountered early-mid last year. With the help of @Steve-Mcl this issue was mitigated, but we never quite figured out what caused it.
PPS:
We are working with multiple people on the same instance, which we feel is a part of the problem. We've also had a couple of occasions where near-simultaneous deployment of modified flows results in a completely empty editor, with a Merge warning. Continuing to do a full deploy in that situation will completely erase all flows in the instance, only having the snapshot as fallback.
Remedy here is to refresh the browser, after which all flows will be visible again (but any changes are lost).
Not sure if this should be a separate bug report, if so let me know..
Expected Behavior
Project returns do not stop returning messages.
Steps To Reproduce
We have not found a way to reliably reproduce this behaviour. Which is also why we've waited to report this as this is very elusive.
However we are positive this is happening.
Environment
FlowFuse version: FF2.11
Node.js version: 20.18.0
Browser: Chromium-based, Mozilla-based
Will add more info as we progress with this issue.
The text was updated successfully, but these errors were encountered:
Question: with Project Request nodes, it's status is displayed as connected.
I assume this is for the connection to the Project In node.
But shouldn't there be a status indication for the Project Return as well?
Current Behavior
Hi,
We're experiencing issues with Project nodes again.
When sending messages through a Project Request node, everything works fine up until, at some time, return messages are not being sent back.
The flow the message is being sent to keeps working, only the return (from a Project Out - Return) is not processed properly, or at all.
We can remedy the problem by changing the time-out of the Project node and redeploying. After that action the flow return works as expected (and the flow returns a message well with the time-out period, like 4s where time-out is 60s). It appears the Project node settings need to be altered, just restarting the flows (Full Deploy) appears to not make a difference.
Currently, we're setting up a Catch trigger so we get notified when a Project node times out. We see this happening but at the moment we have no idea how often this is happening.
PS:
This issue is very much similar to the issue we encountered early-mid last year. With the help of @Steve-Mcl this issue was mitigated, but we never quite figured out what caused it.
PPS:
We are working with multiple people on the same instance, which we feel is a part of the problem. We've also had a couple of occasions where near-simultaneous deployment of modified flows results in a completely empty editor, with a Merge warning. Continuing to do a full deploy in that situation will completely erase all flows in the instance, only having the snapshot as fallback.
Remedy here is to refresh the browser, after which all flows will be visible again (but any changes are lost).
Not sure if this should be a separate bug report, if so let me know..
Expected Behavior
Project returns do not stop returning messages.
Steps To Reproduce
We have not found a way to reliably reproduce this behaviour. Which is also why we've waited to report this as this is very elusive.
However we are positive this is happening.
Environment
Will add more info as we progress with this issue.
The text was updated successfully, but these errors were encountered: