In the original ProfileSubmitServlet (or in the new ProfileProcessor) when processing multiple requests an error for one request may affect the processing for subsequent requests. It's not clear yet whether this is intentional or a bug.

See the following code:

String errorCode = null;
for (int k = 0; k < reqs.length; k++) {
    try {
        ...
        profile.submit(authToken, reqs[k]);
        ...
    } catch (Exception e) {
        errorCode = ...
    }
    if (errorCode == null) {
        profile.getRequestQueue().markAsServiced(reqs[k]);
    } else {
        profile.getRequestQueue().updateRequest(reqs[k]);
    }
}

The errorCode is null initially, then it will be set to a certain value if a request fails. However, the errorCode is not reset to null before processing the next request, so even if the next request works fine it will have the errorCode from the previous request. The errorCode is used to determine whether to call markAsServiced() or updateRequest() for each request.