Filter returned images from SentinelHub using JS-code in layer configuration

Additionally, I found that no-data values are stored differently on the Sentinel2 bands. The no-data values are stored as 1 in band 1 to 3 and as 0 (zero) in band 4 to 12, see for example this image https://services.sentinel-hub.com/ogc/wms/[INSTANCE_ID]?SERVICE=wms&BBOX=509485.0%2C6091690.0%2C509765.0%2C6092090.0&FORMAT=image%2Ftiff%3Bdepth%3D32f&CRS=EPSG%3A32632&WIDTH=56&HEIGHT=80&LAYERS=S2-L2A&REQUEST=GetMap&TIME=2017-02-22T08%3A40%3A30%2F2017-02-22T12%3A40%3A30&MAXCC=5.0&Downsampling=BILINEAR&Upsampling=BILINEAR&Transparent=False&ShowLogo=False.

For different no-data values for different bands - are you sure this is not a result of interpolation? You should observe data on natural resolution (depending on each band).

It is currently not possible to “skip” the scenes with nodata values.
You can however do a pre-fetch call using Statistical API as discussed here:

Hello! Thanks for your quick reply, that information helps, but as the idea es to work without the need of looking at the images, it would be great to get the nodata cover value. Thanks!!