Skip to content

feat(recurring): add max_executions — auto-deactivate after N executions#367

Open
Leothosine wants to merge 1 commit into
Lead-Studios:mainfrom
Leothosine:feat/issue-190-max-executions
Open

feat(recurring): add max_executions — auto-deactivate after N executions#367
Leothosine wants to merge 1 commit into
Lead-Studios:mainfrom
Leothosine:feat/issue-190-max-executions

Conversation

@Leothosine
Copy link
Copy Markdown

Summary

Adds max_executions (0 = unlimited) and execution_count to RecurringRecord. execute_recurring increments the count and automatically deactivates the payment when max_executions is reached.

Changes

  • Add max_executions: u32 and execution_count: u32 fields to RecurringRecord
  • execute_recurring increments execution_count after each transfer
  • Auto-deactivates and emits recurring_completed event when limit is reached

closes #190

@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented May 30, 2026

@Leothosine Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

feat: add max execution count to recurring payments — automatically deactivate after N executions

1 participant