You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
500 error doesn't highlight the problem with endpoint itself. It's just default value for odata response
I do expect the process to wait until both requests are resolved and then respond with the relevant content. However, it appears that only one of the two requests is executed, triggering a global response (batch request itself). The second request simply returns a default 500 error with empty content, which is default values for OData response object.
The problem as discussed during our committee meeting is that we reuse same processors through all batch request handling flow but should create new instance of Processor per each request.
Here is current flow where same subProcess promise is used for handle several request inside of one batch request.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
if there are 2 requests in a batch, one of them fails. But if you try the request separately, it works.
http://localhost:3000/backend/odata/hcmtanalysis/$batch
gives the following response:
Expected Behavior
all provided batches should be handled
Steps To Reproduce
No response
Environment
Relevant log output
No response
Anything else?
500 error doesn't highlight the problem with endpoint itself. It's just default value for odata response
I do expect the process to wait until both requests are resolved and then respond with the relevant content. However, it appears that only one of the two requests is executed, triggering a global response (batch request itself). The second request simply returns a default 500 error with empty content, which is default values for OData response object.
The problem as discussed during our committee meeting is that we reuse same processors through all batch request handling flow but should create new instance of Processor per each request.
Here is current flow where same subProcess promise is used for handle several request inside of one batch request.
The text was updated successfully, but these errors were encountered: