apache/dolphinscheduler · error · ServiceException

10001

10001

Error message

request parameter {msg} is not valid

What it means

Thrown in UsersServiceImpl.createUser after checkUserParams returns a non-empty message: one of userName, userPassword, email or phone failed format/existence validation. The generic guard fires for any invalid request parameter, and msg names the specific field at fault (e.g. user name exists, email format wrong).

Source

Thrown at dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/UsersServiceImpl.java:132

     */
    @Override
    @Transactional(rollbackFor = Exception.class)
    public User createUser(User loginUser,
                           String userName,
                           String userPassword,
                           String email,
                           int tenantId,
                           String phone,
                           String queue,
                           int state) throws Exception {
        if (!isAdmin(loginUser)) {
            throw new ServiceException(Status.USER_NO_OPERATION_PERM);
        }

        // check all user params
        String msg = this.checkUserParams(userName, userPassword, email, phone);
        if (!StringUtils.isEmpty(msg)) {
            throw new ServiceException(Status.REQUEST_PARAMS_NOT_VALID_ERROR, msg);
        }

        if (!checkTenantExists(tenantId)) {
            log.warn("Tenant does not exist, tenantId:{}.", tenantId);
            throw new ServiceException(Status.TENANT_NOT_EXIST);
        }

        User user = createUser(userName, userPassword, email, tenantId, phone, queue, state);
        log.info("User is created and id is {}.", user.getId());
        return user;
    }

    @Override
    @Transactional
    public User createUser(String userName,
                           String userPassword,
                           String email,
                           int tenantId,

View on GitHub (pinned to 02eac45a1b)

Solutions

1. Fix the parameter indicated in the msg placeholder (user name/password length, email format, phone format)
2. If msg says the user name already exists, choose a different userName
3. Validate input client-side before submitting to avoid repeated rejections

When it happens

Trigger: Thrown at dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/UsersServiceImpl.java:132 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of apache/dolphinscheduler@02eac45a1b (2026-09-06). Data as JSON: /api/errors/1fcb6f10321d14eb. Report an issue: GitHub.