ONClick MF is not getting triggered on PROD Kubernets environment.

0
Below error we are facing on button click on PROD kubernets environment. The MF is not getting triggered.Same logic/code is working in QA enviroment and onclick the REST API is working fine. But in PROD even the first log activity is not working.
asked
2 answers
0

Hi Snehal,

Since the same code works in QA but fails only in Production, this is likely an environment-specific issue rather than a microflow issue.


From the screenshot, the request is failing with an HTTP 500 (Internal Server Error) before the microflow executes. Since even the first log activity isn't reached, I'd check the following:

  • Verify that the runtime logs in the Production pod don't contain any startup or authorization errors.
  • Check whether the REST endpoint, environment variables, constants, or secrets differ between QA and PROD.
  • If you're running on Kubernetes, ensure the pods are healthy and that the ingress/reverse proxy isn't blocking the request.
  • Open the browser's Network tab and inspect the failed request to see the response body—it often contains more details than the console error.
  • Also check if there are any recent deployment or configuration differences between QA and PROD.


Could you also share the runtime logs around the time of the button click? The browser console only shows that the request failed with a 500 error; the runtime logs will help identify the actual root cause.


Kindly mark this as the accepted answer if it helps.

answered
0

Added one screenshot. But still the first log activity in MF is not logged

answered