Hi Fly team,
I’m posting this because the current org slug behavior is very confusing and, honestly, quite frustrating from a user perspective.
I’m trying to secure an exact org slug for branding.
My preferred order is:
-
acent
-
acenthq
Here’s what I’m seeing:
-
flyctl orgs show acent returns “Could not find”
-
flyctl orgs show acenthq returns “Could not find”
-
But when I try to create orgs with those names, Fly does not give me the exact slug and instead creates suffixed slugs such as:
-
acent-69
-
acent-641
-
acenthq-338
-
That behavior is hard to understand.
From the user side, it looks like:
-
the slug does not exist
-
the CLI says it cannot be found
-
but the exact slug is still not actually available
If a slug is unavailable, it would help if Fly clearly said it is unavailable.
If it is reserved internally, it would help if that were visible.
If deleted slugs cannot be reused immediately, that should be documented somewhere.
Right now it’s very difficult to know whether these slugs are:
-
actually taken
-
temporarily reserved
-
permanently blocked
-
or recoverable with staff help
That uncertainty makes org naming much riskier than it should be.
So I’d really appreciate a clear answer on the following:
-
Is acent still blocked internally even though flyctl orgs show acent returns “Could not find”?
-
Is acenthq also blocked internally for the same reason?
-
If so, is that temporary or permanent?
-
Is there any official policy or documentation around deleted/unavailable org slug reuse?
-
Can Fly staff help release or restore one of these exact slugs?
My requested priority is still:
-
acent
-
acenthq
If either of those exact slugs can be restored or assigned, that would solve the issue.
Thanks.