Recherches récentes

Pas de recherche récente

Don McCall's Avatar

Don McCall

Adhésion le 16 avr. 2021

·

Dernière activité le 12 déc. 2022

Suivis

0

Abonnés

0

Activité totale

10

Votes

0

Abonnements

6

APERÇU DES ACTIVITÉS

Dernière activité effectuée par Don McCall

Don McCall a créé une publication,

Publication Developer - Zendesk APIs
MS Flow Zendesk trigger stopped working

On Nov 20th sometime after 9am pacific, Both the "When an Item is Created" and "When an Item is Modified" triggers in the Flow/Zendesk connector stopped working.  Returning an error that "The response is not in a JSON format."   Other calls using the standard API respond correctly.

Flow gives me little insight into what could be causing this.  Were there any changes to the API in that timeframe? any other ideas?

All I get from Flow is 

{
    "statusCode": 400,
    "headers": {
        "Set-Cookie": "ARRAffinity=ca7c46c3c31662c75d55b74e76f40f531eebe8abea76034cc43fa51d9c4747f3;Path=/;HttpOnly;Secure;Domain=zendesk-ncus.azconn-ncus.p.azurewebsites.net,ARRAffinitySameSite=ca7c46c3c31662c75d55b74e76f40f531eebe8abea76034cc43fa51d9c4747f3;Path=/;HttpOnly;SameSite=None;Secure;Domain=zendesk-ncus.azconn-ncus.p.azurewebsites.net",
        "Timing-Allow-Origin": "*",
        "x-ms-apihub-cached-response": "false",
        "x-ms-apihub-obo": "false",
        "Date": "Mon, 12 Dec 2022 22:13:17 GMT",
        "Content-Length": "616",
        "Content-Type": "application/json"
    },
    "body": {
        "error": {
            "code": 400,
            "source": "flow-apim-msmanaged-na-westus-01.azure-apim.net",
            "clientRequestId": "f778043b-fda2-4b8f-9127-50fa3590d849",
            "message": "The response is not in a JSON format.",
            "innerError": "\r\nBad%C2%A0Request\r\n\r\n

Bad%C2%A0Request%C2%A0-%C2%A0Request%C2%A0Too%C2%A0Long

\r\n

HTTP%C2%A0Error%C2%A0400.%C2%A0The%C2%A0size%C2%A0of%C2%A0the%C2%A0request%C2%A0headers%C2%A0is%C2%A0too%C2%A0long.

\r\n\r\n" rel="nofollow noreferrer">http://www.w3.org/TR/html4/strict.dtd\">\r\nBad Request\r\n\r\n

Bad Request - Request Too Long

\r\n

HTTP Error 400. The size of the request headers is too long.

\r\n\r\n"
        }
    }
}

Publication le 12 déc. 2022 · Don McCall

0

Abonnés

2

Votes

1

Commentaire

Don McCall a ajouté un commentaire,

CommentaireUsing themes and customizing your Help Center
Product guides

I am trying to use the media info to hide some elements when printing a KB article.  I see syntax in the CSS Sheet that uses the media width to style "@media (min-width: 1160px)"

Does anyone know how to structure a CSS entry for Zendesk that will apply a style if the Media is "Print"

Afficher le commentaire · Publication le 09 juin 2022 · Don McCall

0

Abonnés

0

Votes

0

Commentaire

Don McCall a ajouté un commentaire,

Commentaire de la communauté Feedback - Ticketing system (Support)
Communauté

+1 Agree, this would be a great addition.  constantly scanning down the list trying to remember which ones I have looked at or not is not productive.  should be able to 'check off' an item to remove it from the list or remove it once it has been clicked on.

Afficher le commentaire · Publication le 12 avr. 2021 · Don McCall

0

Abonnés

1

vote

0

Commentaire

Don McCall a ajouté un commentaire,

Commentaire de la communauté Feedback - Ticketing system (Support)
Communauté

I agree with this thread.  We do not allow users to submit tickets via Email in order to ensure some structure, but the inability to add screenshots and images by pasting into the ticket creation or when adding content to the conversation in "My Activities" is a major pain point.  Forces users to save image as a file and then attach which is a big experience pain point.  

Please address this.

Afficher le commentaire · Publication le 20 juin 2019 · Don McCall

0

Abonnés

0

Votes

0

Commentaire