#Action strings bug install
#Action strings bug code

Process exited before completing request: this typically happens if your script completes without calling callback.Lambda expects callback to be there to complete an async function, so it'll produce errors if it's redefined. NoneType object does not support item assignment: this error can happen when you redefine some of the important variables in the function, such as callback.Scripting payload too large: this means the total amount of data returned from your function is too large.Some common error messages you might encounter include: fetch is already included in the namespace.

#Action strings bug code

Only the standard node.js library and the fetch package are available in the Code by Zapier app.

#Action strings bug install

You cannot require external libraries, or install or import libraries commonly referred to as 'npm modules'.Your Zap will hit an error if it exceeds these limits. Paid users can run scripts of up to 10 seconds and 256 MB of RAM. Free users can run scripts of up to 1 second and 128 MB of RAM.For instance, don't return an entire JSON structure, just the keys you need. If you're hitting this error, try to limit the amount of data returned from your function. The total size of the code and the data processed by the Code step cannot exceed that. The environment in which your Code steps run (AWS Lambda) has an I/O limit of 6 MB.The test step in the editor can be used for a tighter feedback loop.

Your Zap History will have all relevant details around the Code step's inputData, output and logs.

Running your Zap via the dashboard is the canonical way to confirm the behavior you expect.

StoreClient : a built-in utility for storing and retrieving data between Zap runs.

The logs are returned in a runtime_meta added automatically to the output. You'll need to test your Zap to see the values.

console.log: this utility allows you to debug your function.

Subsequent invocations to callback(err, output) will be picked up by the next execution of your Zap, but will not affect that task's execution, other than side effects like console.log() calls. If you have multiple asynchronous calls, each invoking callback(err, output) with their desired responses, only the first one to execute will count. Invoking callback(err, output) tells Zapier that your task is done executing.