MOBIUSI INCThis dataset contains source code snippets and verification annotations for notification delivery, retries and backoff, deduplication keys, idempotent writes, and failure recovery. Its fields cover workflows such as notification creation, delivery, acknowledgment, retry, and recovery, with assessments of retry policies, concurrency safety, persistence, and recovery logic. It is designed for code review, defect localization, root-cause analysis, and reliability verification of notification systems.
| Field | Type | Description |
|---|---|---|
| file_name | string | File name |
| source_code | string | A source code snippet to verify, related to notification delivery, retries, or idempotency. |
| recommended_fix | string | Actionable recommendations for addressing identified retry, deduplication, idempotency, or recovery issues. |
| confidence_score | number | A quantitative score for confidence in the verification conclusion, typically ranging from zero to one. |
| test_case_summary | string | A summary of concurrency, timeout, duplicate-message, and failure-recovery tests for reproducing issues and validating fixes. |
| invalid_retry_risk | boolean | Indicates whether the implementation risks retrying when it should not, exceeding retry limits, or omitting necessary retries. |
| root_cause_analysis | string | Analysis of the triggering conditions, defect location, concurrency timing, and underlying causes of identified issues. |
| verification_verdict | string | The overall conclusion of the code verification. |
| notification_loss_risk | boolean | Indicates whether the implementation risks leaving a notification undelivered, unrecovered, or incorrectly discarded. |
| implementation_language | string | The primary programming language or technology stack identified from the source code. |
| retry_policy_assessment | string | Assessment of the maximum retry count, retryable error conditions, stopping conditions, and retry scheduling logic. |
| verification_annotation | string | Original annotations, execution results, and evidence records produced by manual or automated verification. |
| duplicate_broadcast_risk | boolean | Indicates whether the implementation risks broadcasting or delivering the same notification more than once. |
| state_inconsistency_risk | boolean | Indicates whether delivery, storage, or consumption states may become inconsistent. |
| notification_flow_summary | string | A structured summary of notification creation, delivery, acknowledgment, retry, and recovery flows. |
| backoff_strategy_assessment | string | Assessment of fixed delays, exponential backoff, jitter, and backoff limit implementation. |
| failure_recovery_assessment | string | Assessment of recovery and compensation logic for delivery failures, process interruptions, timeouts, and dead-letter handling. |
| idempotent_write_assessment | string | Assessment of persistent writes, uniqueness constraints, conditional updates, and safety under repeated execution. |
| deduplication_key_assessment | string | Assessment of deduplication key generation, scope, validity period, and concurrency safety. |
| Authorization Type | Proprietary - Commercial AI Training License (No Redistribution) |
| Commercial Use | Requires exclusive subscription or authorization contract (monthly or per-invocation charging) |
| Privacy and Anonymization | No PII, no real company names, simulated scenarios follow industry standards |
| Compliance System | Compliant with China's Data Security Law / EU GDPR / supports enterprise data access logs |

Post a request and let data providers reach out to you.
@dataset{Mobiusi2026,
title={Notification Retry and Idempotency Code Verification Dataset},
author={MOBIUSI INC},
year={2026},
url={https://www.mobiusi.com/datasets/7ec937add97db8cc42bb4e10ac8d4c60},
urldate={2026-10-27},
keywords={notification retry code,idempotency verification,message delivery retry,notification deduplication,exponential backoff,failure recovery,duplicate broadcast detection,code root-cause analysis},
version={1.0}
}Using this in research? Please cite us.