When using the new WMTS feature readers, if the service returns a 4xx or 5xx for a tile, it leaves it as blank and continues on with a warning message in the logs. When a tile returns a 200, but with unreadable content, it makes the full feature reject.
There should be an option for how to handle these errors. In my case the way a 200/invalid data tile is handled is what I would want for a 4xx or 5xx error.
I've had to create a little Lambda proxy inbetween FME server and the EMTS to make this happen.
