Today some users accessing the staging env app got this error. Any idea what that means (beside the obvious)? I can access the app just fine from my location
I noticed, this appears to anyone but on specific issue. If related to the issue then I will try to minimize the issueData request with:
/rest/api/3/issue/${issueKey}?expand=renderedFields&fields=-attachment,-comment,-worklog
Still the error appears when I try to submit a form and I could only find this explanation online Solved: Plugin Webhook 413 error (atlassian.com)
As the night arrived I could test my idea on the staging environment. And it proved right, skimming down the issueData retrieval made things work.
So it seems like a capacity limitation of some kind. Not sure what. Solution was more gut feeling than logic. Some explanation should be added to docs, etc.
Hey Richard,
Was the information in this issue particularly large in size? A 413 status code is typically related to the payload size.
Yes. I was retrieving a complete issue from Jira. Then I disabled all comments, all worklogs, all attachments and got rid of the excess baggage, no more error
1 Like
I am also getting this error when clicking on a button. The function doesn’t do anything only console.log.
1 Like
@VladimirVirlan I too have run into this issue with onClick and like you the button only calls console.log. The app loads fine at first, but it seems when it is clicked it is running into a problem with a useState async call that fetches a large number of issues. Unfortunately I have not been able to find a solution. Were you able to figure out a workaround?
1 Like