• Dan Ross

  • October 15, 2019 15:24

  Community Moderator

  Hey Liam,

  When you get this error, can you right click and select 'Inspect' or 'Inspect Element'? There's a window that will appear and it will have a menu that says 'Console'. Once it's open, try hitting save and see if a new error appears. That might provide some more detail. 

  There's limited things we can do in the community for errors like these. You may need to contact the Zendesk Support team to investigate deeper.

• Liam Mcfarlane

  • October 15, 2019 15:36

  Hey Dan,

  Thanks for the tip, it comes up with a couple of errors shown below.

  

  To be honest I contact Zendesk support this morning but heard nothing back so thought i'd try the community.

• Dan Ross

  • October 15, 2019 18:56

  Community Moderator

  Hey Liam,

   

  A 403 means forbidden which is usually a permissions issue. Either you don't have permissions to edit the article or something's gone wrong on the back end. I would add this screenshot to the ticket, it will help the Support team diagnose the issue.

• Stacey Kosch

  • October 21, 2019 14:55

  I'm getting the same error and the same report back. Were you able to get up and running? I'm trying to embed a newsletter we created through Mailchimp. 

• Brett Bowser

  • October 21, 2019 17:00

  Zendesk Community Manager

  Hey Stacey,

  It looks like this issue could be related to an expired session. More information here: Cookies, sessions, and staying signed in

  Are you able to replicate this issue in an Incognito window at all? Are other admins on the account able to replicate this issue?

  Let me know!

• Stacey Kosch

  • October 21, 2019 17:28

  I can replicate in an incognito window, as well as another agent recreating it.

• Brett Bowser

  • October 21, 2019 18:53

  Zendesk Community Manager

  Thanks Stacey,

  I'm going to generate a ticket on your behalf so our Customer Advocacy team can dig into this.

  You'll receive an email shortly stating your ticket has been created.

  Cheers!

• Liam Mcfarlane

  • October 22, 2019 09:00

  Just to let you know, with my one ZD support were unable to come up with a solution, however, out of nowhere it just started working again. Definalty seems to be a bigger issue with Zendesk, especially as it only affects pages with custom code on.

• Jarek Glowacki

  • November 13, 2019 14:09

  Just got this same error recently.

  As suggested above, it turns out my session had expired.

  Keeping my article-editing window open, I span up a separate tab, logged into Zendesk anew, returned to my article tab and was able to save without the error this time.

  Would be nice if the error could mention expired session, or offer a re-log popover without leaving the page.

  But at least the current cryptic error is easily googleable. :)

• Nicole Saunders

  • November 14, 2019 20:18

  Zendesk Community Manager

  Thanks for sharing, @...! Sounds like this is definitely a session expiration issue. 

  I think we should write up a quick article about this. Is "Translation wasn't saved" the specific error? Anything else I should include? 

• Jarek Glowacki

  • November 15, 2019 00:13

  Hi Nicole

  Yep, in my case "Translation wasn't saved" meant "Session expired".

  Nothing further to add.

• Suzie Baunsgard

  • February 25, 2021 20:18

  When it happened today I found a cache clear/hard refresh cleared up the issue. 

Please sign in to leave a comment.