Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Reduce level of asynchronous workflow error log. (#266)
--Currently, whenever an error is encountered in Fili during response processing, we log it in two places: 1. Where the error occurred as an `ERROR` level message. 2. When the Observable stream that saves the job to the ApiJobStore encounters the error, even if "saving" is a no-op because there isn't a job store set up (the current case for everyone using Fili). While it may be useful to know that a value has not been stored in the job store once a customer starts using asynchronous queries, for now it clutters up people's logs with red herrings. The long term solution is to rethink how we handle errors during asynchronous processing so that the logging can be as transparent as the processing. But since nobody has the bandwidth to tackle that right now, instead we lower the log level to debug. That way we aren't just silently swallowing the error, but neither do we clutter up logs set at the standard `INFO` level.
- Loading branch information