Context
The pledge service already tracks attempt records in src/services/pledge.service.ts, but the public or admin-facing workflow does not expose a consolidated view of those attempts in a way that is easy to review. This makes it difficult to understand failures, retries, or campaign-specific pledge behavior.
Problem statement
Add a clear admin-facing view of pledge attempt history so that attempts, status, failure reasons, and retry counts can be reviewed efficiently.
Current behavior
- The service can list attempts for a pledge, but there is no dedicated endpoint or data shape that makes those attempts easy to consume in an operational workflow.
- Attempt details are not surfaced in a consolidated way.
Required behavior
- Admin users should be able to retrieve pledge attempt history for a given pledge in a structured format.
- The response should include the key attempt fields such as status, retry count, failure reason, and timestamps.
- The implementation should remain consistent with the existing pledge service pattern.
Constraints
- The change should preserve the current pledge model and service architecture.
- No new backend infrastructure is required.
Acceptance criteria
Out of scope
- Adding a full dashboard or UI for pledge monitoring.
- Reworking the pledge execution engine.
Hints and references
- Review the existing pledge controller and route structure to add the history endpoint in the same style as other admin views.
Context
The pledge service already tracks attempt records in src/services/pledge.service.ts, but the public or admin-facing workflow does not expose a consolidated view of those attempts in a way that is easy to review. This makes it difficult to understand failures, retries, or campaign-specific pledge behavior.
Problem statement
Add a clear admin-facing view of pledge attempt history so that attempts, status, failure reasons, and retry counts can be reviewed efficiently.
Current behavior
Required behavior
Constraints
Acceptance criteria
Out of scope
Hints and references