alguno ha tenido problemas con sus flujos en n8n alojados en railway en donde funcionan al principio y luego ya no corren donde se argumenta que es por que los flujos fueron creados en versiones de n8n anteriores y en los url o json hay supuestamente signos = adicionales que detienen el flujo supuestamente ....pero lo raro es que funcionaban bien ....y luego plantean la solucion de crearlos desde cero para eliminar el error y nuevamente despues de volverlos a hacer se bloquean .... los revisas y nuevamente argumentan que esta contaminado con versiones de n8n anteriores ....alguien realmente ha encontrado el problema de fondo a esto ? y como solucionarlo ....

tambien cuando comparten flujos de trabajo llegan con problemas ... no se ejecutan ... por lo tanto es un problema del railway ? agradezco que me den luz en esto ya que no esta dejando ejecutar los flujos creados ...

Has anyone experienced problems with their N8n workflows hosted on Railway? They work initially, then stop running. The explanation given is that the workflows were created with older versions of N8n, and supposedly there are extra equal signs (=) in the URLs or JSON that are halting the flow. The strange thing is that they were working fine before. Then the solution is to recreate them from scratch to eliminate the error, and after recreating them, they crash again. You check them, and again they claim it's contaminated with older N8n versions. Has anyone actually found the root cause of this problem and how to fix it?

Also, when I share workflows, they encounter problems... they don't execute. Is this a Railway issue? I would appreciate any insight into this, as it's preventing the created workflows from running.