Welcome to the Changelog! With a large number of upgrades coming soon, this week we shipped a big upgrade to the Talk to an Engineer feature which should make it far easier to get technical support, request a demo, report a bug, and more.
Let’s jump in!
Talk to an Engineer Upgrades
Since we’re now serving hundreds of thousands of developers, it’s been difficult to scale Discord-based support. To meet the increasing demand on our Support Team during this phase of growth, we’ve been building-out tools for users to more easily communicate with our technical staff.
This week we upgraded the Talk to an Engineer form to help deliver you faster responses to your most pressing platform issues.
We now provide a series of options to better categorize your issue or question, provide project information and context, and define urgency. We’ve also added easy ways to request a demo and report a bug.
The additional resolution and context will help us provide better and more timely support moving forward.
To use the new form, simply look for the Talk to an Engineer button in the User menu within the Railway app.
Stacks to Represent Replicas for Priority Boarding
We’ve made a small change to the canvas to display replicas as a stack behind each service. This feature is now available in Priority Boarding.
We’re going to be making some additional improvements to the canvas over the coming weeks, including the addition of attached volumes.
That’s all we can say about this for now, so stay tuned!
Variable Highlighting
Previously it was difficult to visually identify reference variables within service settings.
We’re now decorating variable references with a subtle background to make it easier to see when you’re interpolating variables and regular text.
Improvements and Fixes
- We fixed an issue that caused plugin logs not to display for some users
- We improved log query performance
- We fixed an issue where our proxy re-tries some HTTP 4xx/5xx responses from user applications
- We fixed a visual bug with the logs filtering module
- We fixed an issue with log timestamp formatting