Program auto suspension helps you prevent overspending and maintain control over your bounty budget. When a program’s budget left falls below the platform threshold, the program automatically suspends to avoid exceeding allocated funds. This to ensure that researchers will be paid on time for their work.
How auto suspension works
When a submission is created, the platform places the corresponding bounty amount in a validation until a final decision is made about its validity during review by the triage team or your organization. As a result, a portion of your program’s budget may be temporarily unavailable for new submissions. If the remaining budget drops below the auto-suspend threshold, the program automatically enters suspension. While suspended, researchers can still view the program details but cannot submit new findings.
If your program is suspended:
Review pending submissions promptly to free up any budget in validation.
Add additional budget to maintain a sufficient buffer.
Work with your Customer Success Manager for guidance if the program repeatedly suspends, as this may impact researcher experience.
💡Note: Stay informed and react quickly when your program suspends by enabling program activity notifications. To receive program auto-suspension emails as a company administrator, make sure you have enabled Program activities in your communication preferences (User > Preferences > Communication preferences) and that notifications are turned on for the desired programs (Program > More > Members > Notifications).
By understanding these mechanics, you can proactively manage program budgets, minimize interruptions, and maintain a smooth experience for researchers.
Best practices
Monitor program budgets regularly to ensure active programs do not reach their auto-suspension threshold unexpectedly.
Enable low budget notifications to proactively alert company administrators before a program’s budget falls too low.
Enable program activity emails to receive notifications when a program is auto-suspended, allowing for reactive follow-up.
Consider enabling dynamic budget pooling for programs with high submission volumes to prevent interruptions.
Related articles