In post-1.4.0 deployments, the grabber was pulling the confounds metadata file (desc-confounds_regressors.json) since it matched all queried fields and came first alphabetically, resulting in a processing error. Specifying the extension appears to have resolved the issue.
In post-1.4.0 deployments, the grabber was pulling the confounds metadata file (
desc-confounds_regressors.json
) since it matched all queried fields and came first alphabetically, resulting in a processing error. Specifying the extension appears to have resolved the issue.