When an accounts report of premium API calls has been exhausted the raw exception is output into the console. Ideally these should be captured, in such an event (I believe) execution should end and the current finding stored in the database as this scenario will not change so retrying after a timeout out will not rectify the issue.
When an accounts report of premium API calls has been exhausted the raw exception is output into the console. Ideally these should be captured, in such an event (I believe) execution should end and the current finding stored in the database as this scenario will not change so retrying after a timeout out will not rectify the issue.