Console logging an Error causes {"error":"Function returned invalid status code: 0. Raw body: empty.last"}

[marktani]

Issue by radicand
Sunday Dec 03, 2017 at 21:13 GMT
Originally opened as https://github.com/graphcool/prisma/issues/1359

---

If an error during a function is encountered, and one attempts to log the error with console.log(e) (where e is an Error object), then the framework will instead log a generic {"error":"Function returned invalid status code: 0. Raw body: empty.last"}.

There's a possibility it may just be that logging an Object in general causes this, but I haven't tested that.

Reproduction
Initialize a new project, and create a function that throws an error in a try block. Catch it and attempt to console.log the error. You can also try applying the google auth template, and calling googleAuthentication with a bad token (which will trip into this logic path).

Expected behavior?
The Error to be logged.

Possibly related issues:

• #1320

Moved from:

• #1031

[marktani]

Comment by chinclubi
Wednesday Dec 06, 2017 at 14:24 GMT

---

I also have this error message too

{ error: "Function returned invalid status code: 0. Raw body: empty.last" }

this issue has disappeared after console.log is removed.
is there any progress on this issue??

[marktani]

Comment by marktani
Wednesday Dec 06, 2017 at 14:31 GMT

---

Do you have any insights into the shape of the error object?

Could you try running console.log(JSON.stringify(e)) instead?

[marktani]

Comment by mark-james
Thursday Dec 07, 2017 at 03:23 GMT

---

I'm also getting this error fairly regularly. I've updated all my error handling and console logs to use e.message. There are no JSON.stringify calls anywhere in the function.

This issue is very frustrating as debugging becomes very time consuming.

[marktani]

Comment by grimunit
Thursday Dec 07, 2017 at 08:02 GMT

---

I have been getting the same error. I've been using the stripe integration code from the webshop example. The very first console.log(event); is what seems to be what was causing it. Once I commented that out I started actually getting the correct errors/logs coming through.

[marktani]

Comment by sbornia
Thursday Dec 07, 2017 at 23:09 GMT

---

Happening to me also. Error goes away when logging error.message instead of error.
Not sure this information helps, but in my case the error was just that I was trying to call .split() on a null value. Maybe that helps you guys figure out what the structure of the error object is.

[marktani]

Comment by dohomi
Friday Dec 08, 2017 at 00:32 GMT

---

I was having this issue due to a swolloed hard error on a synchronous function. I was using jwt.sign synchronous, after changing the code to promise based handling the error was printed out correctly

[marktani]

Comment by heymartinadams
Monday Jan 22, 2018 at 04:51 GMT

---

Happened to me, too. Once I got rid of all console.logs such as console.log(`Created stripe customer: ${customer.id}`) the CLI showed the errors correctly.

[vitalbone]

Same thing happening as above; ie, once I removed the console.logs I was able to see the correct error message.

[0xchimz]

I got the error (again) when trying to return an array of object that length more than x element. The size of the array depends on the size of each element, etc

• if I return with object { x: i }, the size of the array that returns without an error is more than 400 elements.
• if I return with object { x: i, yyyyyyyyy: i, aaaaaaaa: i, ..... }, the size of the array that returns without an error is less than 40 elements.

finally, I can't find an actual size of whole response that can return without an error (I will find out soon)

[janzheng]

I'm getting this error when I log too many things, especially complex objects. I think there's probably a size limit to the output of the console log—if that gets too big we get this error. Only log exactly what you need and it won't break

[jhalvorson]

I'm getting a similar issue as described by @janzheng, when I was logging simple strings then everything was okay but if I tried to log a full object, such as a user type with nested data then I received the error.

[heymartinadams]

Basically, this error occurs when attempting to console.log an object in Graphcool’s serverless functions (Graphcool is going away by July 1, 2020, so this issue will become irrelevant pretty quickly anyhow). You can get rid of this error by doing this:

console.log(JSON.stringify(obj_to_be_logged))