apache/dolphinscheduler · error · ServiceException

Not supported

Error message

Not supported

What it means

execStreamTaskInstance in the API ExecutorServiceImpl is an unimplemented stub that always throws a plain ServiceException("Not supported"). Stream task execution through this API entry point is not supported by this build; it exists only to satisfy the interface contract.

Source

Thrown at dolphinscheduler-api/src/main/java/org/apache/dolphinscheduler/api/service/impl/ExecutorServiceImpl.java:398

            throw new ServiceException(Status.TASK_GROUP_QUEUE_ALREADY_START);
        }
        taskGroupQueue.setForceStart(Flag.YES.getCode());
        taskGroupQueue.setUpdateTime(new Date());
        taskGroupQueueMapper.updateById(taskGroupQueue);
    }

    @Override
    public void execStreamTaskInstance(User loginUser,
                                       long projectCode,
                                       long taskDefinitionCode,
                                       int taskDefinitionVersion,
                                       int warningGroupId,
                                       String workerGroup,
                                       String tenantCode,
                                       Long environmentCode,
                                       Map<String, String> startParams,
                                       int dryRun) {
        throw new ServiceException("Not supported");
    }
}

View on GitHub (pinned to 02eac45a1b)

Solutions

1. Use the standard (batch) workflow execution APIs instead of the stream-task entry point.
2. Run stream tasks through the supported execution path in your distribution, or upgrade to a version/distribution that implements stream task execution.
3. Remove calls to execStreamTaskInstance from integrations.

Example fix

// before
executorService.execStreamTaskInstance(loginUser, ...); // always throws
// after
executorService.execute(loginUser, projectCode, workflowCode, CommandTypeEnum.START_PROCESS, ...);

try { execStreamTaskInstance(...); } catch (ServiceException e) { if ("Not supported".equals(e.getMessage())) { /* fall back to standard workflow execution API */ } else throw e; }

When it happens

Trigger: Calling execStreamTaskInstance via ExecutorService (e.g. through the stream-task execution API path) with any parameters — every call throws unconditionally.

Common situations: A client SDK or route wired to the stream-task API on a deployment where stream tasks are not implemented; migrating code that used stream tasks in a different distribution.

Related errors

• no master server available
• Backfill workflow failed: %s
• The workflow instance: %s status is %s, can not pause
• WorkflowInstance: %s pause failed: %s
• WorkflowInstance: %s pause failed

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