Not sure if it's related to the Demo server issue ...
# orm-help
h
Not sure if it's related to the Demo server issue or my code, but I copied the code directly from the tutorial
d
It could be - we have identified a handful of projects that need to be fixed from our end. Can you please try to change the stage name and deploy again? I will unblock your project for this stage tomorrow :)
Let me know if this works for you.
s
Hey Chase. I finished the tutorial and there was no problem. Give it another try. P.S the datamodel.graphql is datamodel.prisma. I am not sure about the file name and I can't check it now as it's 1 am in india.
h
I reverted everything and redid
Copy code
prisma init
Copy code
Creating stage dev1 for service awaitingchanges √
Deploying service `awaitingchanges` to stage `dev1` to server `prisma-us1` 684ms

Changes:

  User (Type)
  + Created type `User`
  + Created field `id` of type `ID!`
  + Created field `name` of type `String!`
  + Created field `updatedAt` of type `DateTime!`
  + Created field `createdAt` of type `DateTime!`

Applying changes (0/5) |
Still stuck on 0/5
d
Are you using US region? I think there is an ongoing issue there. Can you try EU for the moment? It is a bit slow but functional.
h
EU works
👌 1
d
Demo US region is up again, try it with a new service name if the existing one still throws an error on deploy. Please let me know if that works.
h
US worked, deploy time 489ms, Applying changes 16.0s Thanks soo much for getting this fixed so quickly