# Zendesk connector partly broken **URL:** \ **Category:** Elastic Search\ **Tags:** elastic-workplace-search\ **Created:** [July 28, 2022, 11:02am UTC](https://discuss.elastic.co/t/zendesk-connector-partly-broken/310856 "2022-07-28T11:02:46Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![Zetanova](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zetanova/32/108970_2.png) [@Zetanova](https://discuss.elastic.co/u/Zetanova)\ **Post date:** [July 28, 2022, 11:02am UTC](https://discuss.elastic.co/t/zendesk-connector-partly-broken/310856/1 "2022-07-28T11:02:46Z")
I am posting my issue here, because I could not find the zendesk connector source on github, Is it close-source? If there is a better place to post it, please inform me. I added the zendesk connector and the jobs "incremental" and "delete" are working fine, but the "full" job errors from the beginning. The full job expects the "X-Rate-Limit" response header, but i think it is ""X-Rate-Limit-Limit" and/or "x-rate-limit-remaining" ```auto Error after less than 5 seconds Updated 0 items Failure caused by: KeyError: key not found: "X-Rate-Limit" ``` I uploaded the diagnostic bundle here: > ---
**Author:** ![Sean\_Story](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sean_story/32/69987_2.png) [@Sean\_Story](https://discuss.elastic.co/u/Sean_Story)\ **Post date:** [July 28, 2022, 1:54pm UTC](https://discuss.elastic.co/t/zendesk-connector-partly-broken/310856/2 "2022-07-28T13:54:52Z")
Hi @Zetanova > I could not find the zendesk connector source > on github, Is it close-source? It is closed-source, yes. Enterprise Search is making incremental progress in opening select components (including our connectors), but at this time our Zendesk connector is not in a public repo. > The full job expects the "X-Rate-Limit" response header, > but i think it is ""X-Rate-Limit-Limit" and/or "x-rate-limit-remaining" It's actually getting responses of `x-rate-limit` instead of `X-Rate-Limit`. Zendesk has been made aware of this issue - they seem to have changed the casing of their header without notice. We expect our next releases to contain a fix, but in the mean time, I encourage you to raise a support request with Zendesk to request that they restore the original casing of this header. ---
**Author:** ![Zetanova](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zetanova/32/108970_2.png) [@Zetanova](https://discuss.elastic.co/u/Zetanova)\ **Post date:** [July 29, 2022, 7:02am UTC](https://discuss.elastic.co/t/zendesk-connector-partly-broken/310856/3 "2022-07-29T07:02:01Z")
The general convention is to lower http-header and compare. Meaning that user posted header values are always lowered and all header in the http-response too. But off course a case insensitive string compare operator works too. AWS WAF, MS Exchange rules and multiple other popular services are working like that. ---
**Author:** ![Zetanova](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zetanova/32/108970_2.png) [@Zetanova](https://discuss.elastic.co/u/Zetanova)\ **Post date:** [July 29, 2022, 7:02am UTC](https://discuss.elastic.co/t/zendesk-connector-partly-broken/310856/4 "2022-07-29T07:02:52Z")
@Sean_Story Thanks for your response. ---
**Author:** ![Zetanova](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zetanova/32/108970_2.png) [@Zetanova](https://discuss.elastic.co/u/Zetanova)\ **Post date:** [July 29, 2022, 7:56am UTC](https://discuss.elastic.co/t/zendesk-connector-partly-broken/310856/5 "2022-07-29T07:56:53Z")
@Sean_Story zendesk ticket is open ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [October 31, 2022, 2:48am UTC](https://discuss.elastic.co/t/zendesk-connector-partly-broken/310856/6 "2022-10-31T02:48:07Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.