English (US)
  1. Zendesk help
  2. Support
  3. Support advice and troubleshooting
  4. Apps and integrations

Slack target: Error during transmission: HTTP client call failed

Madison Davis
  • Edited
Zendesk Community Team

Question

What should I do if I test my Slack target and get the error Error during transmission: HTTP client call failed?

Answer

This error typically occurs when editing or reviewing the Slack target under Settings > Extensions > Targets. The Slack integration uses OAuth to authentication Zendesk with Slack to allow Zendesk data to be posted to Slack.

However, URL targets have the option to include Basic authentication credentials (username and password) which is not required for this target. When entering these credentials and testing the target, this error is displayed but the integration should be working as expected. 

If Zendesk updates are not posting to Slack, it is recommended to uninstall, then reinstall the Slack app under Admin > Apps > Manage. If you find that updates are still not pushing to Slack, contact Zendesk customer support for further investigation.

Return to top
Have more questions? Submit a request

10 Comments

  • Tran Ba Quy

    hi, I have same problem, whenever I try to test, it returns "Error during transmission: HTTP client call failed", what should I do now?

    0
  • Nicole S.
    Zendesk Community Team

    Hi Tran - 

    Uninstall, then reinstall the Slack app under Admin > Apps > Manage. If you find that updates are still not pushing to Slack, submit a ticket to support@zendesk.com for further investigation.

    0
  • Mike Uy

    Are you serious with this solution?

    I have a dozen slack channel integrations setup. Will I have to recreate all of those if I do this?

    0
  • Michel

    Hello Tran and Mike, 

     

    This is indeed a generic solution and, if we want to see what exactly happened we would need to look into specific errors of these failures. 

    Since this will require more account specific troubleshooting. I'll send you both a proactive ticket to get to specific errors you might see on your end. 

    This is why we are asking you to contact us at support@zendesk.com if you are facing some issues, we would need to know what the exact error is to be able to determine what is happening. 

    Talk to you soon. 

    Cheers

    0
  • Becca
    Zendesk team member

    Hi everyone - 

    Sorry for all the confusion this issue has caused! I have gone ahead and edited this article with more concrete information surrounding the error. Let us know if you have any questions!

    0
  • Alex Gerulaitis
    • Edited

    Our Slack integration just got disabled with the same generic message:

    "The target '<custom> Slack Integration' has been temporarily disabled due to too many failures. You can re-enable the target from Settings -> Extensions -> Targets to continue sending messages to the target, but please check the possible reason of these failures by testing the target first."

    Testing the integration produces "Error during transmission: HTTP client call failed".

    Immediate questions:

    1. What are the failures and related error messages?
    2. How long have they been going on, how frequently, ratio of failures vs. successes? Is there a log of error messages anywhere? If not why not?
    3. How was the "too many failures" part determined? How is the decision to disable an integration made? If the errors started awhile ago, why weren't we notified first, before disabling the integration?

    (No proactive notifications of failures? No error log? Just kill the app? Seriously?)

    0
  • Alex Gerulaitis

    "Test Target" button does not work on any of our integrations, including that are working otherwise.

    Looks like it's a bug.

    0
  • Guy Dee

    Hi Alex! I'm sorry to hear about the trouble.

    In response to each of your immediate questions above:

    1. These error messages can be found on the Target Failures tab of the API dashboard under Admin > Channels > API. This list shows the response code, target name, and timestamp of the failure. Click on any individual record to see details about it, including the complete content of the request sent to the target, and the complete content of the target's response.
    2. The Target Failures tab should give a good impression of how long an issue has been ongoing for a particular target and how frequent it is. As noted above, detailed records of the response are recorded for every failure.
    3. A target is automatically deactivated if it fails 21 consecutive times with no successes (documented at the bottom of our article on target notifications). There is no lifetime or historical maximum for failures; the limit is only for consecutive failures. When a target is automatically deactivated in this way an email notification is sent to the account owner.

    I hope this information is helpful!

    1
  • Alex Gerulaitis
    • Edited

    Thanks Guy!

    • Accessing that log (Admin > Channels > API) required accepting API ToC even if all we wanted was the logs. Not sure if this is intended behavior - doesn't seem logical to me: if creating an integration doesn't require accepting new terms, accessing related logs shouldn't either.
    • Re: "target disabled" incident last week in our Zendesk instance, there are no log entires at all for that day. There is only one failure in the logs for the entire first half of 2018. I.e. we have no logs for that failure.
    • "Target disabled" emails sent to the owner of an instance should be sent to all admins - else the integration can suffer a much longer downtime due to lack of critical notifications. The owner (e.g. the principal of the business units or the purchasing agent) may not relay the critical notification until well into the downtime.
    • "Target disabled" emails should absolutely link to the logs - or at least mention their existence, and relevant KB articles - else an admin is spending time hunting down relevant KB articles vs. attempting to resolve the issue.
    • As mentioned in my previous comment, "test target" button always produces an error for us, including for targets that are working.
    • APIs / integrations should have a mechanism to proactively notify instance admins of failures, errors and warnings. Sending an email to the account owner only after the target is disabled is no way to treat an issue. (Would you prefer the "check engine" light to turn on once an issue is detected - or only after the engine dies?)

    Thank you again for the help.

    0
  • Guy Dee

    Hi Alex -

    It sounds like this might be better handled in a support ticket where we can gather details about any issues you're experiencing. I'll reach out in a ticket shortly!

    0

Please sign in to leave a comment.

Related articles

Powered by Zendesk