apache/dolphinscheduler · error · ServiceException
10001
10001
Error message
request parameter {0} is not valid What it means
Thrown by validateMissedFirePolicy (called from insertSchedule and updateSchedule) when the MissedFirePolicy supplied with a schedule is not one of the allowed enum values. It is a generic parameter-validation guard; the faulting input is the missed fire policy string in the schedule request body.
Source
Thrown at dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/SchedulerServiceImpl.java:605
schedule.setWorkerGroup(workerGroup);
schedule.setEnvironmentCode(environmentCode);
schedule.setUpdateTime(now);
schedule.setWorkflowInstancePriority(workflowInstancePriority);
scheduleDao.updateById(schedule);
workflowDefinition.setWarningGroupId(warningGroupId);
workflowDefinitionDao.updateById(workflowDefinition);
log.info("Schedule update complete, projectCode:{}, workflowDefinitionCode:{}, scheduleId:{}.",
workflowDefinition.getProjectCode(), workflowDefinition.getCode(), schedule.getId());
return schedule;
}
private void validateMissedFirePolicy(ScheduleParam scheduleParam) {
if (scheduleParam.isMissedFirePolicySet() && scheduleParam.getMissedFirePolicy() == null) {
log.warn("Schedule missed fire policy is invalid.");
throw new ServiceException(Status.REQUEST_PARAMS_NOT_VALID_ERROR, "missedFirePolicy");
}
}
}
View on GitHub (pinned to 02eac45a1b)
Solutions
- Use a valid MissedFirePolicy value, e.g. CONTINUE or FAIL.
- Check the API documentation for the accepted enum names and casing.
- Fix the client-side form/enum mapping that produced the invalid value.
Defensive patterns
Strategy: validation
When it happens
Trigger: Thrown at dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/SchedulerServiceImpl.java:605 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/714469b7cae2cf9e.
Report an issue: GitHub.