Fitbit date queries outside a range of 3 years throw a 500

[ezulo]

I'm making a call to the shimmer to retrieve some Fitbit data for a given user. However, I'm getting this error:

{"timestamp":"2019-05-07T14:03:08.842+0000","status":500,"error":"Internal Server Error","exception":"org.openmhealth.shim.ShimException","message":"org.springframework.web.util.NestedServletException: Request processing failed; nested exception is org.openmhealth.shim.ShimException: A request for Fitbit data has failed.","path":"/data/fitbit/step_count"}

when trying to query step count data for a user outside of a 3 year window. For example, requesting data with date queries of [2016-05-01, 2019-04-01] will return OMH data, but [2016-05-01, 2019-05-02] will fail with the above error.

Up to this point I hadn't been aware that there are any limits on date ranges. Is this expected behavior from the shimmer or a bug?