Important points to note:

I've tested the code on my local machine and Render without any errors.

I've tried several solutions, including redeploying the instance, adjusting .env settings, and even starting a new project from scratch, but the error persists.

I've also contacted the Flowise team, and they confirmed that the functionality works on their end.

That link returns HTML so the angle bracket character makes complete sense.

How are you deploying flowise to Railway?

Via GitHub

Right, but more specifically, are you using a template or is this a full manual deployment?

Either way, if you already in contact with the flowise team, it would be best to ask them what was configured incorrectly.

I was in contact with them, and as I said before, the app works fine on local machine or other cloud providers.

It is only here on Railway where I am facing this error.

Your deployment on Railway would be missconfigured.

This would not be an issue with the platform.

Please look into what misconfigurations could cause such an issue with the flowise team.

"Please look into what misconfigurations could cause such an issue with the flowise team."

I already did that.

I am trying to get help here, on RAILWAY.

I have reported that I source my deployment from the same fork (a clone of Flowise repository) on my local manchine, RENDER and here on Railway.

It is here, only on Railway where I face this error.

I'm sorry but this is support for Railway, not flowise.

Your flowise is missconfigured on Railway, that doesn't mean there is an issue with Railway Itself, this is solely an issue with your deployments configuration.

Unfortunately running locally and on another cloud provider does not mean the issue is with Railway Itself, again, this issue is a misconfiguration with your deployment.

My god, you really are wasting my time here.

I see in your profile that you dont work for RAILWAY, right? "I don't work for Railway".

Can you allow me to try to get help from the RAILWAY team as their paying customer?

I am not deploying any of my instances manually, it is RAILWAY system who is deploying it for me. So if there is something wrong with the deployment, it is caused for RAILWAY. And that is why I am here, to try to get help.

I'm sorry you think I'm wasting your time, but you would get better support for flowise from the flowise team or their community.

Can you allow me to try to get help from the RAILWAY team as their paying customer?

I'm sorry but Hobby users are not eligible for support from the team unless it is a platform or billing issue, this issue is neither.

I am not deploying any of my instances manually, it is RAILWAY system who is deploying it for me. So if there is something wrong with the deployment, it is caused for RAILWAY

You are, you are choosing where to deploy the service from, you are choosing all the environment variables, you are choosing all the configurations, etc etc, if flowise isn't working as intended it's because something is missconfigured on your end, and the flowise team and or community would be able to give you far better help with flowise than the Railway community can.

AGAIN? You are being very rude, here.

It is a platform ISSUE and I explained why. I do not accept your technical explanations since you do not work from RAILWAY.

Waiting for a response from the RAILWAY TEAM.

This is not an issue with the platform, the team does not assist Hobby users unless it is a platform or billing issue.

It is.

Waiting for a response from the RAILWAY TEAM.

Sorry, but it is not a platform issue. Please seek support for flowise from the flowise team and or community.