0dcee768-317a-406e-8fe5-33133601d48d

!t

note - not a limited trial

Ok, I think I did find the issue.

Free plan resource provision limit exceeded. Please upgrade to provision more resources!
You can see that error pop up at the end of my video.

This makes sense. I guess. But even if that is the real issue, that is the error message that should be shown. And not just "Oh No" 😄

1251258371504472106

is 3 projects really the trial plan limit??

interesting

It isn't a 3 project thing. I get hit with the error on the second project.

Also, even if there is a liimit like that, it still doesn't explain the resource showing up in the manage service part of the danger tab. But not showing up in the actual project Architecture section.

And also not showing up for the first video I sent; but showing up when I did it not on video. Buggy behavior regardless

yeah very buggy, will wait to see what a team member says

To continue on with the inconsistent behavior, when adding a repo, I get this message and the little error toast. So I do see that you have a proper error message available. It just isn't showing up for all routes of hitting that limit 👍

Wait no, this still doesn't make sense. Is a volume a service? Becuase I wouldn't think that it is, but that would be the only way I am hitting 5 services. Seeing as I only have this one project

volumes shouldn't be counted, they aren't services, but you might have 5 of something across your entire account

I don't think so:

then I'm not sure, we are back to waiting for a team member to shed some light on this

hmmm agree this all seems buggy.. gonna spin up a ticket for us to fix the trial flows. @Joshie are you able to test drive the platform properly in the meantime?

Yea. I was able to complete all the tests I needed to for actually evaluating railway. I am going to meet with the team in a few days to discuss if we should migrate over or not.
I was more so wanting to test a few extra things without the need of removing BBWare. But I might just have to. <:shrug:747680403778699304> doesn't really bother me too much

you had to remove it because of the limitations? happy to see what i can do to bump those up for you, so you can do everything you need

otherwise thanks for providing the feedback on the Trial experience, we definitely need to make that better

I didn't remove it yet. But I am working with a mono repo. And the first time I was messing with things, I could have sworn the UI reacted one way over another. But without being able to add a new blank project to test it, I won't know if I am just remembering wrong or I actually found a bug.

Basically, I could have sworn that when I linked a repo, the option to provide a root directory went away. But I see it now? Was going to see if I could reproduce it. Or if I was just blind

i wonder if it's because the UX changes after you've added the repo

i feel like i got confused by this when we first changed it. like it goes from an input to a link that you have to expand

Yes, that! It shouldn't become a link! I didn't see that link! Especially becuase if it is filled out, it remains. It should stay consistent. Made figuring out mono repo stuff just a little harder and confusing. I will add a feedback thread and copy that over.

that's really great feedback. funny how i had the same reaction as you, but obviously got used to it and became blind. i'm sure plenty of others have gotten frustrated by it. a thread will be perfect, and i'll mention it internally as well

we've been pushing to make our first time user xp better, so this is hugely appreciated. anything else that comes to mind, please shout it out

Oh I have been 😄
Should I just open each thing as feedback threads? I don't want to clog the thread. But then again, it is helpful to keep each item separate (when it makes sense to)

yeah it sounds like you have a feel for the feedback thing, so whatever makes sense. if it's tedious to have individual threads, you could also just create one that's like "feedback on first time user experience" and catalog everything underneath

if it's nits, you can just drop em here too tbh. but for like big things, like feature requests, those are prime for threads

nit would be like the root directory thing above. feature request would be like "add a configurable firewall"

The one other thing (that I can think of right now) is small to say but big to implement / fix.
The fact that a trial plan machine has access to 32vCPU. So that if I try to spin up workers based on core count, it crashes due to using up too much memory and CPU.

vouch, long standing issue, not just for trial, also affects hobby

though it doesn't actually have access to that many cores, it only thinks it does

Ok ok. Well yea; not sure how you would go about fixing that. I don't know enough about the internal infra. But I can only assume it would require a good bit of rework.

To continue on with the buggyness; Suddenly, I was able to add a blank service without the error. Yay. But I deleted it (never deployed it anything) and then ,,,
I now have a ghost service. 😄
So that is fun. If I had to guess, I would say that this is a system wide issue that is only being noticed becuase the trial account has limits that are easy to hit. Regardless -- here are your more data points