Extracting stack trace from an exception could provide useful information, especially when you work on platforms where you can deploy custom Java code, exception handling is done by the platform, and exceptions from your custom-written Java code are masked by default platform exceptions.

Typical messages you see from these exceptions logged or shown on the platform UI would be: "Unable to Execute API," "Something went wrong," etc.

Catching these custom exceptions in your own Java code and logging them should be good practice to solve the above-mentioned problem.

public static void extractStackTrace(Exception exception, Logger _logger) {

 StackTraceElement[] elements = exception.getStackTrace();
 String trace = null;
 for (StackTraceElement element: elements) {
  trace = (trace == null) ? element.toString() : trace + ",\n" + element.toString();
 }
 _logger.error(log);
}

This way you have access to stack trace for debugging in the logs, while the platform where you deploy your code does not give you this information.