I encounter this Error on my Production
The things is even I have checked log on Service Center, the error is still way too general info for me to debug:
Where I think the bug happen is right at the aggregate at start of screen, maybe some thing fell off from there, but I don't know anyway to specific the bug or monitor/debug it
Usually if an aggregate failed, what will you do to debug it?
(My aggregate contain a filter which is a result of another aggregate run at start too - but I don't think this is the root cause - yet)
Hello,
If I want to check whether the aggregate is fetched or not in production, I would inspect the Network tab in the browser DevTools or review the related data items associated with it.
If the aggregate is fetched inside a Data Action, the corresponding action request will also appear in the Network tab.
If the issue is not in production, I would start a normal debugging session in Service Studio to trace the execution flow.
Also, if two aggregates are fetched on screen initialization and one depends on the other for filtering purposes, this could potentially cause issues. There is no guaranteed execution order unless explicitly controlled, so this should be verified as well.
Another point to consider is that a 403 status code generally indicates unauthorized access. If the screen loads without issues and only the popup appears, there might be an action throwing an exception with a 403 status code, such as an API call. This should also be checked.
Hi @Huy Le ,
It's correct, u must open DevTool and review the network tab. Errors may occur during page load.
For the 403 error shown below, you first need to determine whether it is caused by the source code or not.
Usually, this type of 403 error is related to Role/Permission issues, invalid or missing Header/Auth Token, and similar authorization problems. Since these cases are often difficult to identify just by checking the Service Center logs, you should instead verify the logic inside the source code — especially the role checks, authentication/authorization flows, and any server actions or REST authentication that may be blocking the request.