Hello, I am now suddenly getting this error, was w...
# prisma-whats-newr
ragnorc
06/20/2017, 9:03 AMHello, I am now suddenly getting this error, was working previously: Error: GraphQL error: Whoops. Looks like an internal server error. Please contact us in Slack (https://slack.graph.cool) and send us your Request ID: cj45cag0p0b5c0120gwej57we
n
nilan
06/20/2017, 9:29 AM@ragnorc I'm looking into this right now. could you please PM me your project id?
r
ragnorc
06/20/2017, 9:30 AMGreat, thanks!
g
gb
06/20/2017, 10:15 AMsame here - Request ID: cj45etmix0fke0146sh84rrb3",“requestId”:“cj45etmix0fke0146sh84rrb3"
n
nilan
06/20/2017, 10:16 AMHey @gb can you pm me your project id? 🙂
g
gb
06/20/2017, 10:17 AMgb
06/20/2017, 10:18 AMI had just changed the Job schema to use an enum for the status
gb
06/20/2017, 10:20 AMSorry - if i remove status from the returned field list the query works
gb
06/20/2017, 10:22 AMYour brilliant UI warned me that it was a breaking change (bravo). I still went ahead and it would appear to have resulted in this behaviour
n
nilan
06/20/2017, 10:22 AMWhat are the possible enum values?
g
gb
06/20/2017, 10:23 AMPending, Scheduled, WIP
gb
06/20/2017, 10:23 AMAt the moment, it will expand over time
t
tomhut
06/20/2017, 10:27 AMAlso seeing an internal server error
tomhut
06/20/2017, 10:28 AMRequest ID: cj45fev3524az0148ve3jdd35"
tomhut
06/20/2017, 10:33 AMHumm, seems to be when the response is rather large
g
gb
06/20/2017, 10:33 AMOnly 4 docs retuned in my case
gb
06/20/2017, 10:34 AMThere should only be 1
t
tomhut
06/20/2017, 10:35 AMInfact in my case it seems to be when the request is very large
n
nilan
06/20/2017, 11:29 AMok @tomhut that seems to be a different issue, I'll reach out to you in a PM 🙂
nilan
06/20/2017, 11:29 AMsame for you @gb 🙂
4 Views