Your n8n service does not appear to have a volume attached, and Railway's filesystem is ephemeral, meaning any data written to disk (including n8n's default SQLite database where workflows are stored) is lost on redeploy. If you had previously set up volume backups, you could restore from one, but without a volume the data from the previous deployment is not recoverable. Going forward, attaching a volume to your n8n service will ensure workflow data persists across redeploys.