Backend: Add campaign auto-deactivation job when endDate passes

[CelestinaBeing]

Summary

Campaigns with an endDate remain marked active: true in the DB forever after their end date passes — unless an operator manually calls PUT /api/v1/campaigns/:id to deactivate them. An automated background job should deactivate expired campaigns and optionally call the on-chain set_active(false) if a contract is linked.

Problem

In backend/src/index.js, the jobRunner only runs rpc_health_poll. There is no job that checks for expired campaigns.

Acceptance Criteria

• Add campaign_expiry_check job to jobRunner that runs every 5 minutes (configurable via EXPIRY_CHECK_INTERVAL_MS)
• Job queries: SELECT * FROM campaigns WHERE active = 1 AND endDate IS NOT NULL AND endDate < NOW()
• For each expired campaign: set active = false in DB, write an audit log entry with actor system:expiry-job
• If campaignContractId is set and the backend has an admin key configured (STELLAR_ADMIN_KEY env): build and submit set_active(false) transaction to the campaign contract
• Emit campaign.deactivated webhook event (when webhooks from issue Backend: Add webhook/notification system for campaign events #287 are available)
• Add unit tests: campaigns past endDate are deactivated, campaigns before endDate are untouched, campaigns without endDate are untouched
• Log all auto-deactivations at INFO level

References

• backend/src/jobs/jobRunner.js
• backend/src/index.js — job registration

[HuyadO4]

@HuyadO4 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

Hi maintainer, I would love to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @HuyadO4 to this issue.

[legend-esc]

@legend-esc has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work on this issue because automatically deactivating expired campaigns is an important consistency and reliability improvement that prevents stale campaigns from remaining active indefinitely in both the backend and potentially on-chain state. Automating this process reduces operational overhead, improves data integrity, and ensures frontend users are not presented with expired campaigns as still active.

I have experience implementing background job systems, scheduled maintenance tasks, and blockchain-integrated backend workflows, and I’m comfortable building reliable automation that safely synchronizes off-chain and on-chain state transitions. For this issue, I would focus on extending the existing job runner in backend/src/index.js with a scheduled campaign-expiration task that identifies campaigns whose endDate has passed and automatically marks them inactive in the database.

I would also implement optional on-chain synchronization logic to call set_active(false) when a linked contract exists, while ensuring failures in blockchain interaction do not corrupt backend state or halt the scheduler. Particular attention would be given to idempotency, retry-safe behavior, structured logging, and efficient querying so the job remains safe and performant as campaign volume grows. In addition, I would add tests covering expired campaigns, already-inactive campaigns, missing contract links, and partial-failure scenarios to ensure the automation behaves reliably under real-world conditions.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @legend-esc to this issue.

[presidojay1]

@presidojay1 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I would like to work to on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @presidojay1 to this issue.

[drips-wave]

Congratulations, @presidojay1! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 2, 2026.

🧑‍💻 @presidojay1: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊

[drips-wave]

This issue has been completed by @presidojay1 as part of the Stellar Wave Program's 5th Wave 🥳

😎 @presidojay1: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.