How to find the internal error details from Atlassian?

sivasighakolli

Noticed few of these errors when calling jira api to create issues. We try to create tickets automatically based on the application error. Can we find what the internal error is? This is inetrmittent issue and retrying again works.

• Endpoint:
  POST /rest/api/3/issue

• Details:

• Error type: 500 - Internal server error

• Log reference: be937dc5-add3-4ced-8dd3-00c6f9b86c61

• TraceId: 914820ea2c274420a431ecf029c35035<br><br>Failed to create notification. Status -> InternalServerError | Response -> <!DOCTYPE html><html lang="en"><head><meta charset="utf-8"><meta http-equiv="X-UA-Compatible" content="IE=edge"><title>Oops - an error has occurred</title><link type='text/css' rel='stylesheet' href='/static-assets/metal-all.css' media='all'><script src='/static-assets/metal-all.js'></script><meta name="decorator" content="none" /></head><body class=" error-page error500"><script type="text/javascript">document.body.className += " js-enabled";</script><div id="page"><header id="header" role="banner"></header><!-- #header --><section id="content" role="main"><div class="aui-page-panel"><div class="aui-page-panel-inner"><section class="aui-page-panel-content lowerContent"><div id="error-state"><span class="error-type"></span><h1>Something went wrong</h1><p>Try reloading the page, then check our <a href="<a href="https://status.atlassian.com" rel="noopener nofollow noreferrer" target="_blank">https://status.atlassian.com</a>">Statuspage</a> for any current outages. If there are no relevant outages, create a <a href="<a href="https://support.atlassian.com/contact/" rel="noopener nofollow noreferrer" target="_blank">https://support.atlassian.com/contact/</a>">support request</a> so we can help you out.</p><p>If you create a request, include the following so we can help you as fast as possible:</p><ul><li>Error type: <strong>500 - Internal server error</strong></li><li>Log reference: <strong>be937dc5-add3-4ced-8dd3-00c6f9b86c61</strong></li><li>TraceId: <strong>914820ea2c274420a431ecf029c35035</strong></li></ul></div></section><!-- .aui-page-panel-content --></div><!-- .aui-page-panel-inner --></div><!-- .aui-page-panel --></section><!-- #content --><footer id="footer" role="contentinfo"><section class="footer-body"><div id="footer-logo"><a href="<a href="http://www.atlassian.com/" rel="noopener nofollow noreferrer" target="_blank">http://www.atlassian.com/</a>" rel="nofollow">Atlassian</a></div></section></footer><!-- #footer --></div><!-- #page --></body></html> | ReferenceId -> metric-mioffice-cashboxdata-staging-alert-20260120

John Funk

HI @sivasighakolli 

Often times 500 errors are related to not having configurations adequately setup or overloading the server with too much at one time. I have seen many of these when you have a lot of custom fields with very few custom Contexts created for the (vs. using just the global context).