[Backend] PAUSED/RESUMED worker handlers skip the dedup guard used by all other events

[ogazboiz]

Telegram: https://t.me/+DOylgFv1jyJlNzM0

Why this matters

In backend/src/workers/soroban-event-worker.ts, every event handler (handleStreamCreated, handleTokensWithdrawn, handleFeeCollected, etc.) checks tx.streamEvent.findUnique({ where: { transactionHash_eventType } }) and skips/upserts to avoid duplicates on replay. But handleStreamPaused and handleStreamResumed call tx.streamEvent.create(...) directly with no dedup guard.

Given the @@unique([transactionHash, eventType]) constraint in schema.prisma, a replay (/v1/admin/indexer/replay) of a ledger containing a pause/resume will throw a unique-constraint error mid-transaction for those handlers, which is inconsistent with the restart-safe behaviour of the rest of the worker (#381).

Acceptance criteria

• Make handleStreamPaused and handleStreamResumed use the same find-then-upsert-with-skip pattern as the other handlers
• Add/extend a worker test that replays a pause+resume and asserts no duplicate rows and no thrown error

Files to touch

• backend/src/workers/soroban-event-worker.ts (handleStreamPaused, handleStreamResumed)

Out of scope

• Governance event indexing ([Backend] Indexer ignores fee_config_updated and admin_transferred governance events #524).

[Senorespecial]

please assign this project to me i have experience in it and can deliver professionally

[clintjeff2]

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

Hello, I have 6 years of experience working on tasks like this and handling similar challenges across backend, frontend, and smart-contract development. I have carefully read and fully understood the task requirements, and I am confident I can deliver a clean, efficient, and well-tested solution promptly. I always ensure high-quality implementation, maintainability, and adherence to best practices.

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

[Deyanju23]

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

I would like to resolve this issue.

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

[pchieneye]

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

Hello, I would like to work on this issue and deliver solution that meets the acceptance criteria.

Thank you.

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

[Chigybillionz]

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

Hi, I’m interested in this task and can handle the implementation. Assign it to me and I’ll get started.

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

[sweetesty]

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

Hi can I be assigned to this issue

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

[Power70]

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

Hi maintainer,

I can work on this issue

Kindly assigned it to me

Thank you

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

[drips-wave]

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

🧑‍💻 @sweetesty: 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 🌊