From 3b3e9afde8a798e7d565941c86c0f74ba598a94e Mon Sep 17 00:00:00 2001 From: mblackstock Date: Wed, 2 Oct 2019 16:34:02 -0700 Subject: [PATCH] README changes --- README.md | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-) diff --git a/README.md b/README.md index c4b812f..6942c13 100644 --- a/README.md +++ b/README.md @@ -164,10 +164,9 @@ The function node generates sample points as follows: return msg; -### Handling Failed Reads and Writes -Errors in the read and writes can be caught using the node-red `catch` -node. Error information is availlable in the default `msg.error` as well -as in the `msg.influx_error`. At time of writing this only includes the -status code from the influx client. The `influx-read` node will -always throw a `503`, whereas the write nodes throw more descriptive -error codes as detailed in the [Influx API documentation](https://docs.influxdata.com/influxdb/v1.7/tools/api/#status-codes-and-responses-2). +### Catching Failed Reads and Writes +Errors in reads and writes can be caught using the node-red `catch` node as usual. +Standard error information is availlable in the default `msg.error` field; additional +information about the underlying error is in the `msg.influx_error` field. Currently, +this includes the HTTP status code returned from the influxdb server. The `influx-read` +node will always throw a `503`, whereas the write nodes will include other status codes as detailed in the [Influx API documentation](https://docs.influxdata.com/influxdb/v1.7/tools/api/#status-codes-and-responses-2).