Repository navigation
TaskType.LAMBDA should be removed — LAMBDA task type is deprecated #427
Description
Summary
TaskType.LAMBDA is present in the SDK's enum (task_type.py line 22) but the LAMBDA task type is deprecated in Conductor OSS and should be removed from the SDK rather than built out.
Current state
from conductor.client.workflow.task.task_type import TaskType
print(TaskType.LAMBDA) # "LAMBDA" — still present in enumThere is no LambdaTask builder class (the absence is intentional, per current understanding).
Requested fix
Remove the LAMBDA entry from TaskType in src/conductor/client/workflow/task/task_type.py.
If any other SDK code references TaskType.LAMBDA, remove or update those references as well.
Context
Original issue asked for a LambdaTask builder. This was reopened and rewritten after confirming with maintainer (@viren-conductor) that the LAMBDA task type is deprecated and should not be supported going forward.
Activity
[-]No LambdaTask builder class — TaskType.LAMBDA exists in enum but is unusable[/-][+]TaskType.LAMBDA should be removed — LAMBDA task type is deprecated[/+]nthmost-orkes commentedon Aug 10, 2026
@v1r3n — quick question before we pull the trigger on removal:
Was
TaskType.LAMBDAleft in the enum intentionally to support existing workflows that use LAMBDA tasks? If so, I'm not sure how the SDK would actually help there — there's no builder class, so users with old LAMBDA workflows are already falling back to raw dicts. The enum entry on its own doesn't seem to provide a migration path.If the answer is "yes, leave it for backward compat," what's the target timeline for full removal? And should we add a deprecation warning in the meantime so users know not to build new workflows against it?