Menu

Implementing NodeJS Retry Logic for Moderation API Timeout Errors in Candidate Scoring
📰

Implementing NodeJS Retry Logic for Moderation API Timeout Errors in Candidate Scoring

DEV Community: api·SullivanReed1247·13 days ago
#CkUCmC6T
#devtoapi#devto#dev#moderation#candidate
Reading 0:00
15s threshold

A moderation timeout should never silently turn into a hiring score. For a B2B SaaS candidate-ranking service, the safe rule is to keep moderation, scoring, and publication as separate states: retry transient transport failures, accept only schema-valid results, and quarantine anything that remains unknown.

That boundary matters more than the retry library. A candidate record can be perfectly parseable while its moderation decision is missing, stale, or ambiguous. I treat those as different failures, with different operators and different recovery paths.

How should a candidate service handle moderation API timeout errors?

The first question is not "how many retries should I add?" It is: "what may the scorer do while the moderation state is unknown?" For this workflow, the answer is no publication and no automatic rejection.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.