🎨 [Frontend] Handle LongRunningTask errors better

[odeimaiz]

What do these changes do?

• Display error message provided by the backend
• Show "No message" text if the flash message is empty

Related issue/s

follows #6444

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[GitHK]

👍

[pcrespov]

In the video attached to the PR, are you using the latest version of the stack, including #6444 ? In theory, after that commit, unhandled exceptions are transformed into 500 with json-response as

{
  "error": {
      "status": 500, 
      "message": "We apologize for the inconvenience. Our team has recorded the issue and is working to resolve it as quickly as possible. Thank you for your patience [OEC: 1234]"
   }
}

and on the web-server logs you should get a comprehensive log with details of the exception including the context

[odeimaiz]

In the video attached to the PR, are you using the latest version of the stack, including #6444 ? In theory, after that commit, unhandled exceptions are transformed into 500 with json-response as

{
  "error": {
      "status": 500, 
      "message": "We apologize for the inconvenience. Our team has recorded the issue and is working to resolve it as quickly as possible. Thank you for your patience [OEC: 1234]"
   }
}

and on the web-server logs you should get a comprehensive log with details of the exception including the context

Nope, the commit wasn't in yet.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud