Blocked from publishing templates

24 days ago

Hello,

My account has been blocked from publishing templates, and I'd like to understand why and ask you to reconsider.

Workspace: 6604266f-53ae-49c5-aaf8-2f3b3054320d

On 11 September 2026, updating the README of my Laminar template (d36cb2b0-fc4f-472a-abc5-29a466301558), I got:

"You have been blocked from publishing templates. Please reach out to the team for more information."

I was adding one paragraph explaining that the egress warning shown on that template's NEXT_PUBLIC_URL variable is expected and safe to ignore. All twelve of my templates are still published and deployable, so I take this as a restriction on publishing rather than a removal of my work.

I don't know what triggered it. Two things may look unusual:

  1. I published three templates in April and nine between 7 and 9, but it's how I work - focused stretches, not automated submission. Happy to space out in future if needed.

  2. I deleted and republished Laminar once. Shortly after publishing Laminar I found its trace search was quietly broken - the search box returned "no results" for every query instead of reporting an error, because the backing search service wasn't deployed. As far as I can tell there's no way to refresh a published template's configuration in place - templateGenerate only takes a project ID, so deleting and republishing was the only route. It had zero deployments at the time, so nobody got caught by it.

Each template is a thin, pinned wrapper around an open-source project, in a public MIT repo under github.com/RockinPaul, deployed and verified before publishing.

Could you please tell me what triggered the block, and what can I do to get it lifted? If one of my templates falls short of your guidelines, I'd like to know which, and I'll fix or withdraw it.

Thank you.

Duplicate

0 Replies

Railway
BOT

24 days ago

It looks like you already have a thread open about this: Laminar. We're automatically closing this one, and we'll reply to you there soon. If you have anything more to add about this topic, please post it in that thread.

Status changed to Duplicate Railway • 24 days ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...