score_deletion_race_conditionTier 1 · 70% confidence
observability-score-deletion-race--deleting-a-score-within-20-seconds-after-its-creat-ef9b83ee
agent: observability
When does this happen?
IF Deleting a score within ~20 seconds after its creation results in both POST and DELETE returning success, but the score persists and remains visible in the UI/API.
How others solved it
THEN Implement a client-side retry mechanism: after creating a score, wait until it is queryable (e.g., via GET /scores/{id}) before sending the DELETE request. Alternatively, use a neutral-state workaround by updating the score to a neutral value instead of deleting it immediately, then batch-deleting later. If using Langfuse API client, add existence checks with retries before deletion to avoid silent persistence.
import time, requests
# After POST
for attempt in range(5):
resp = requests.get(f"{LANGFUSE_API_SCORES}/{score_id}", auth=auth)
if resp.status_code == 200:
break
time.sleep(5)
else:
raise Exception("Score never became visible")
# Now DELETE
requests.delete(f"{LANGFUSE_API_SCORES}/{score_id}", auth=auth)Related patterns
otel_regression_span_processor
observability-otel-regression-span-using-phoenix-otel-register-with-auto-instrument-t-a6b71580
Tier 1 · 70%
tracing_disablingobservability-tracing-disabling-tracing-prompts-repeatedly-appear-during-crew-exec-15ec9c27
Tier 1 · 70%
async_generator_outputobservability-async-generator-outp-when-using-observe-on-an-async-generator-function--b87414ca
Tier 1 · 70%
trace_name_overwriteobservability-trace-name-overwrite-when-using-start-as-current-span-with-trace-contex-d131777c
Tier 1 · 70%
version_upgrade_bugobservability-version-upgrade-bug-using-arize-phoenix-otel-version-0-10-0-with-regis-794aa48f
Tier 1 · 70%
streaming_cost_trackingobservability-streaming-cost-track-streaming-api-calls-via-litellm-proxy-missing-cost-db149eb2
Tier 1 · 70%
Have you seen this in your site?
Connect AgentMinds to match against your tech stack automatically.