See this Comm Center thread. Catch preposterous JD values and fail the observation instead of having an exception bubble up and kill the entire scheduler!