Sean Kane 3266a7deb9 Align standalone activity failure retries with workflow activities (#11250) ...

## What changed?

Moved activity failure retry classification into a shared helper used by
standalone activities, workflow activities, and workflow retries.

Standalone activities now use the same retry classification as workflow
activities for failures reported through
`RespondActivityTaskFailedById`. This includes retryable
`ServerFailure`s, worker-reported start-to-close and heartbeat timeouts,
and otherwise unrecognized failure variants. Schedule-to-start and
schedule-to-close timeouts remain non-retryable.

## Why?

Standalone activities previously treated non-application failures as
non-retryable. Sharing the existing workflow retry classifier keeps
retry behavior consistent across SAA, WFA, and workflow retries.

---------

Co-authored-by: Fred Tzeng <fred.tzeng@temporal.io>

2026-08-04 10:42:29 -04:00

..

retry_policy_test.go

Align standalone activity failure retries with workflow activities (#11250)

2026-08-04 10:42:29 -04:00

retry_policy.go

Align standalone activity failure retries with workflow activities (#11250)

2026-08-04 10:42:29 -04:00