https://www.prisma.io/ logo
Join Slack
Powered by
:warning: Deployment issue. Persists with fresh ac...
# orm-help
s
⚠️ Deployment issue. Persists with fresh accounts with zero addons.⚠️
On Prisma dashboard the dates displays incorrectly as well.
This first happened on a fairly developed web app, when adding a new enum type. Initial idea was that it’s related to the latest deployment, after which all sort of errors started to appear whenever any of 
prisma
CLI commands was fired. - Tried deleting existing services and relaunching, the error persisted. - Tried to create a new account - also persisted - uninstall prisma NPM from local machine, restarted local machine and the errors are gone, however, we’re back to the “Applying changes” issue, which was what initially caused this. Below are some more screenshots from the errors that turned up after the patient-zero deployment
These errors appeared after each 
prisma
command
This was looping over after 
prisma deploy
on a fresh account in the existing project
d
Thanks for the input, can you please share your Prisma CLI version? In my understanding, to replicate. I just need to setup a new service and deploy won't work? Or are there any other steps?
Also, Can you try to change your stage name and deploy again?
s
@divyendu that is correct
I have changed and tried multiple things
also I am part of a channel that uses Prisma to deploy their backends and multiple people are experiencing the same issue
version appears to be 1.23.2
*updating now
d
Thanks! let me try to reproduce this at my end as well.
s
After longer period of time (i left the “Applying Changes (0/5)” to remain working) Got the following error:
a
Is your system clock correct?
d
For me it took a while but eventually it worked, I will report this internally. Do give it another go though?
s
now after attempting to deploy getting the same error that got after the first failed deploy:
@albinekb
d
Can you call the stage dev1 and try again?
s
@divyendu as said - i’ve tried at least 15 times with several scenarios. Also it appears that my case is not an isolated incident
Sure, I’ll try that now
@divyendu just to clarify - you’d like me to create a new Service with the name stage name of dev1, corrcet?
d
Yes
👍 1
If this does not work, please try to use a newer service name as well. I am trying to isolate if this is a generic issue or a specific issue. Thanks for your patience 🙏
s
In progress with new Service name and new Stage new
quick update: still spinning in progress, which is at least 20x the time it normally takes
d
I can confirm this in the US region (at least), notified the team, I will keep you posted about a resolution. EU is very slow but is working. Can you try to deploy to 
eu1
in place of 
us1
? Just to move on and validate this hypothesis for now?
s
Same result happened again just now
@divyendu i’ll try that
d
Thanks for working with me on this and sorry about the inconvenience 🙏:)
s
of course, same for you! thanks for looking into this!
@divyendu ufff.
this worked
so I’m assuming us server is down?
d
Yes, US is down and getting stuck at applying changes. EU is very slow - 25-30 sec for deployments that usually take a few seconds. We are aware of this now, I will notify you once this is fully resolved.
🙌 1
How much time did EU deployment take for you?
h
deploying took 2.3s, Applying changes 21.3s
s
@divyendu it was slower for sure, but wasn’t the end of the world
👌 1
with 240+ changes this was the result with EU server from Toronto, CA: 
Applying changes 28.1s
Thank you for your help, much appreciated, sir! 🙂
👌 1
d
Note: Please do not pin messages unnecessarily. Thanks.
s
@dpetrick thank you Dominic! This, however, was not a personal isolated incident, and thanks to @divyendu assistance we were able to quickly identify the issue. Additionally this enabled me to share the answer with others who had same issue on other Slack channels. My bad on forgetting to unpin, though
d
@ScottAgirs: US is up again, try it with a new service name if the existing one still throws an error. Please let me know if that works
👍 1
s
@divyendu I’ll try in the following days if u don’t mind, we’re catching up with the tasks now, but will definitely follow up
👍 1
d
Sure, please feel free to reach out in case you run into any issues :)
Open in Slack
PreviousNext
Powered by