Ignore invalid step IDs when inserting or replaying tasks

[mnafees]

Description

Fixes a nil pointer panic when a batch of tasks includes an invalid step ID.

Type of change

• Bug fix (non-breaking change which fixes an issue)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
hatchet-docs	Ready	Preview, Comment	Apr 27, 2026 9:58am

[Copilot]

Pull request overview

Fixes a nil-pointer panic in task creation/replay flows by skipping tasks whose StepId no longer exists (e.g., step deleted) before building per-step configuration-dependent fields.

Changes:

• Filter out CreateTaskOpts with missing StepId before calling insertTasks.
• Filter out ReplayTaskOpts with missing StepId before proceeding with replay logic (and log a warning when skipped).

Comments suppressed due to low confidence (1)

pkg/repository/task.go:2395

• The error wrap message here says "failed to get step expressions" but the call is to getConcurrencyExpressions. This makes debugging misleading; update the message to reference concurrency expressions (and keep wording consistent with insertTasks).

	concurrencyStrats, err := r.getConcurrencyExpressions(ctx, tx, tenantId, stepIdsToConfig)

	if err != nil {
		return nil, fmt.Errorf("failed to get step expressions: %w", err)
	}