# Automatic report generation using watcher not able to parse auth

**URL:** <https://discuss.elastic.co/t/automatic-report-generation-using-watcher-not-able-to-parse-auth/364658>\
**Category:** Kibana\
**Tags:** elastic-stack-reporting\
**Created:** [August 9, 2024, 9:19am UTC](https://discuss.elastic.co/t/automatic-report-generation-using-watcher-not-able-to-parse-auth/364658 "2024-08-09T09:19:55Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![jessgarson](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jessgarson/32/129841_2.png) [@jessgarson](https://discuss.elastic.co/u/jessgarson)\
**Post date:** [August 12, 2024, 5:37pm UTC](https://discuss.elastic.co/t/automatic-report-generation-using-watcher-not-able-to-parse-auth/364658/4 "2024-08-12T17:37:53Z")

</div>

Hi @surya_dadi_dhamarake,

This error usually happens when Elasticsearch cannot parse a specific field in the message attachment. It would be best to double-check that your data format is correct for your authentication parameters.

This [related forum post](https://discuss.elastic.co/t/configuring-watcher-with-basic-auth-and-elastic-cloud/132189) might be helpful too.

---

_[View the full topic](https://discuss.elastic.co/t/automatic-report-generation-using-watcher-not-able-to-parse-auth/364658)._