Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

temporal-spring-ai: a provider 429 fails the chat activity on the first attempt

Ouverte
  • Quelque chose ne va pas ?
#3,121 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 2 jours

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
38/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
java, spring
Domaine
backend

Piste de recherche

Start with ActivityChatModel.java:111-114 and the reported ProviderRateLimitRetryTest cases; the issue does not give the test's file path. Compare the activity's retry behavior with Spring AI's default handling of 429 and its inner retries. The issue describes possible approaches but leaves the policy to the team; done should address the reported 429 and 503 cases, including the Retry-After and insufficient_quota distinction.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

Expected Behavior

A rate-limited LLM call (HTTP 429) through ActivityChatModel is retried by Temporal with backoff. sdk-python's OpenAI Agents integration already treats 429 as retryable and passes the provider's retry delay through (temporalio/sdk-python#1796).

Actual Behavior

The activity fails on attempt 1 with RETRY_STATE_NON_RETRYABLE_FAILURE. Spring AI's default error handlers, both the plain builder default and the Boot auto-configured one, turn every 4xx, 429 included, into NonTransientAiException (RetryUtils in Spring AI 1.1.0), and ActivityChatModel puts that type in doNotRetry by default (ActivityChatModel.java:111-114).

A related interaction on 5xx: Spring AI's own RetryTemplate (10 attempts, backoff up to 3 minutes) runs inside the activity, so a persistent 503 can send up to 30 requests across Temporal's 3 attempts. The activity has a 2-minute start-to-close and no heartbeat, so a timed-out attempt can keep calling the provider while later attempts run. sdk-python turned off Botocore's inner retries for its default Strands Bedrock model for a similar reason (temporalio/sdk-python#1797).

Steps to Reproduce the Problem

  1. Point a real OpenAiChatModel at a local stub that returns 429 with Retry-After: 7, register it with ChatModelActivityImpl, and call it from a workflow through ActivityChatModel.forDefault().
  2. The stub sees one request; the workflow gets ActivityFailure caused by ApplicationFailure of type NonTransientAiException, attempt 1.
  3. With a 503 stub and Spring AI's backoff shortened to milliseconds, the stub sees 30 requests.

I have this as a test (ProviderRateLimitRetryTest, five cases, including Boot-equivalent defaults and spring.ai.retry.on-http-codes=429). For a fix I'd rather not parse exception messages, but Spring AI's handlers throw NonTransientAiException with only a message, so the status survives only in the message and the headers are gone by the time the activity sees it. The OpenAI path could instead use a response error handler, scoped to the client Temporal calls, that keeps status, headers and the error body; the activity can then retry rate limits with Retry-After as the next delay and leave insufficient_quota 429s non-retryable, since backoff won't fix a billing limit. Whether the module should also turn off Spring AI's inner retry for calls it wraps seems like your team's call; I'll follow whichever direction you prefer.

Specifications

  • Version: sdk-java main (be01e60a), Spring AI 1.1.0
  • Platform: JDK 21, macOS
Langage dominant
Java
Étoiles
433
Forks
257
Merge moyen
2 j 22 h
PR mergées (30 j)
22

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de temporalio/sdk-java

Toutes les issues de temporalio/sdk-java

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.