Spectrum is now read-only. Learn more about the decision in our official announcement.


🔴 The Prisma Spectrum community is not officially managed by Prisma's support team any more. Please seek help on GitHub or on Slack instead. Learn more:


Prisma watercooler

March 20, 2019 at 8:32am
Show previous messages

August 4, 2019 at 6:59pm

August 29, 2019 at 6:20pm
Hello...Please help me out with this error. already tried changing docker-compose file but same error.
version: '3'
image: prismagraphql/prisma:1.11
restart: always
- "4466:4466"
port: 4466
# uncomment the next line and provide the env var PRISMA_MANAGEMENT_API_SECRET=my-secret to activate cluster security
# managementApiSecret: my-secret
connector: mongodb
port: '4406'
schema: public
user: admin
password: movies
migrations: false
Please do note that changing host: to host.docker.internal also not working

September 3, 2019 at 7:49am
I added field Permission and got this error. Plz help me

September 12, 2019 at 11:23am
Just started getting the same issue using a similar set up to the stack used in Wesbos' sick fits. Was working fine about an hour ago and now this. Should be noted that I also can't view my service in the Prisma Console online.
I've just been on the Intercom chat with one of the reps at Prisma and my services are running fine again! Might be worth doing the same if your are still having that issue!

September 19, 2019 at 7:03am
What the fuck is that plz
Prisma:1.34 container is infinity loop

November 21, 2019 at 9:21am
Hi there,
I have been trying to deploy a new datamodel on an existing Prisma service, but I get the following error:
ERROR: You can not deploy to a service stage while there is a deployment in progress or a pending deployment scheduled already. Please try again after the deployment finished.
"data": {
"deploy": null
"errors": [
"locations": [
"line": 2,
"column": 9
"path": [
"code": 4008,
"message": "You can not deploy to a service stage while there is a deployment in progress or a pending deployment scheduled already. Please try again after the deployment finished.",
"requestId": "local:ck38ht1h80hgf0836ndvrbrvj"
"status": 200
The problem is, it's been in that state for almost 36 hours now and I don't know how to kill that in progress deployment... I have tried restarting the Prisma service container but unfortunately the problem persists after reboot.
Any help would be very much appreciated !

December 28, 2019 at 5:04am
Hey all! Anyone here that can help me with a few questions? One involves and error I'm encountering while building tests and another about some datamodel erros that are getting tossed back at me

July 15, 2020 at 1:57am

July 15, 2020 at 8:08am
Hi, If I remember correctly (it's been a few monthes), I solved it by manually altering the Migration table that prisma uses. I deleted the problematic row and then retried the deployment and it succeeded as expected.

August 2, 2020 at 5:01pm
Hello Everyone I am new to Prisma & I am facing an issue & I am not sure how to resolve it The details are:-
```model Story { id Int (autoincrement()) storyNumber String createdAt DateTime (now()) type String? priority String? title String? state String description String? itemAuthor User (name: "CreatedPosts", fields: [itemAuthorId], references: [id]) itemAuthorId Int itemAssigned User? (name: "AssignedPosts", fields: [itemAssignedId], references: [id]) itemAssignedId Int? }
model User { id Int (autoincrement()) name String email String password String links Link[] votes Vote[] itemCreated Story[] ("CreatedPosts") itemAssigned Story[] ("AssignedPosts") }``` My Mutation Object is:-
postStory(storyNumber: String!, type: String!, priority: String, title: String, state: String!, description: String, storyAssignedTo: Int): Story
The code is:-
const postStory = async (parent, args, context, info) => {
const authorId = getUserId(context);
if (!authorId) {
throw new Error("Missing Token");
let payLoad = {
storyNumber: args.storyNumber,
type: args.type,
priority: args.priority,
title: args.title,
state: args.state,
storyAuthor: {
connect: {id: authorId}
let assignedToUser = await context.prisma.user.findOne({
where: {
id: args.storyAssignedTo
if (assignedToUser) {
payLoad = {
storyAssignedTo: {
connect: {id:}
const newStory = context.prisma.story.create({
data: {
return newStory
Whenever I execute this I get an Error
"data": {
"postStory": null
"errors": [
"message": "\nInvalid `prisma.story.create()` invocation in\n/Users/aditya.padhi/Documents/jiraclonebackend/src/resolvers/Mutation.js:112:43\n\n\n The change you are trying to make would violate the required relation 'StoryAuthor' between the `Story` and `User` models.",
"locations": [
"line": 2,
"column": 3
"path": [
can someone suggest what exactly I am missing.? Thank-You In Advance

September 16, 2020 at 4:28pm
storyAssignedTo and storyAuthor are not Story model properties
storyAuthor should be replaced by itemAuthor and storyAssignedTo by itemAssigned inside your payload

March 23, 2021 at 5:32pm
Hey folks--I have a typescript repo that fails on tsc compilation with type errors. When I run sls package with your typescript plugin, however, it just logs those errors, but continues on its merry way. How do I configure the plugin to fail sls package on typescript compilation errors/warnings?