Additional Note:

As I tried to explain in my previous report, I now have confirmation that this is not, in fact, any sort of "deployment misconfiguration" (as Brody tried to ill-informed me and marked as "solution"). This appears to be an incompatibility of some of their nodes with the Railway platform. Flowise devs are facing the same issues as me when they run their app here on RAILWAY. Yet, Brody ripped away my ability to try to reach the RAILWAY team, hindering further troubleshooting efforts or getting any additional help from the community.

Brody abused the system when, for the sake of winning an argument, he misled the community, Railway Team and myself by marking the unresolved issue as solved. And this behavior is unacceptable and unprofessional.

Hi Frank. There's flow-wise instances running on Railway

If what you're saying is true and the flow-wise devs are having issues, then that's indeed an issue with the application. They may have pushed a new version which breaks. In that case, you should file it with the application devs, and they should raise it with us.

I don't see Brody having done anything wrong here

So, Jake, this is how this works. Please bear with me 1 min here:

As your second class customer from the HOBBY plan I can only get help via this forum, right?

After a lot of debugging, we post here asking for help or a clue about the issue we are facing ONLY here on Railway. BUT no, instead, we face a moderator, that does not work for RAILWAY, that has no clue about what we are reporting, but yet, the guy keeps saying that it was a "deployment issue" when it was, in fact, an incompatibility with some of the nodes.

For the sake of winning the argument, the guy closed the ticket marking as SOLVED an unsolved ticket, preventing us to get any sort help from the community, the only way we have to get some sort of support from Railway.

Since I signed up I know that the support for the HOBBY plan is almost 0, but preventing us to get help from others users in this forum by closing the ticket, it is just unfair.

If this is the way you want to resolve this, what can I do.

And thank you for your reply.

You're welcome to re-open another ticket with "Hey I'm having issues deploying Flowise. Here's my logs"

But if you're going to make the case that this is a "Platform issue", you're going to be rude about it, and ultimately, you're going to be wrong, well, your ticket is 100% going to get closed.

And so he didn't just "close the ticket to win the argument"; he WAS right. And you were rude to people in the community about it.

Personally I think you owe Brody an apology, not the other way around.

I see…

Jake, I did not make any case about a "platform issue" at all, in fact, it was brody who started using that term in the conversation to close the ticket. I cant re open any ticket like "Hey I'm having issues deploying Flowise. Here's my logs" since there is not "deployment issue" here but a incompatibility with some API call nodes on Railway, that, for some reason, only happened here.

So, I do not agree with any of your last statements or the resolution of my complaint, I feel it is very unfair to me, but I do accept you resolved so.

I take this complaint as responded now.

Thank you for your time.