Handle FAILED status in poll

[AbelOsaretin]

Description

Handle FAILED status in the poll_until_confirmed loop. A FAILED status means the transaction was rejected on-chain (e.g., budget exceeded, invalid operation, auth failure).

Current Behavior

FAILED is matched in poll_until_confirmed and returns SubmitError::TransactionFailed with the diagnostic events. This is correct but needs proper error propagation.

Desired Behavior

When FAILED is detected:

1. Extract diagnosticEventsXdr from the response
2. Log at error level with the hash and events
3. Return SubmitError::TransactionFailed { events } immediately (do not retry)
4. The caller (execute_handler or set_prices_on_chain) should record the failure

Implementation Details

"FAILED" => {
    let events = result.diagnostic_events_xdr.unwrap_or_default();
    tracing::error!(hash, ?events, "transaction failed");
    return Err(SubmitError::TransactionFailed { events });
}

• Do NOT retry on FAILED — the transaction is permanently rejected
• Diagnostic events contain Soroban contract error details
• The caller should parse the events to determine if it is a Budget, ExceededLimit (for order freeze logic)

Acceptance Criteria

• FAILED status returns SubmitError::TransactionFailed immediately
• Diagnostic events are captured and returned in the error
• FAILED does NOT trigger a retry
• Error is logged at error level with hash and events
• Unit test: verify FAILED returns error with events

[JoesWalker]

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

Hi maintainers, I'd like to claim this issue!

I’m a Full Stack Developer specializing in Next.js/React (TypeScript + Tailwind) and Node.js (PostgreSQL + Prisma/Drizzle).

My Approach for This Issue
Context: I’ll implement this by [insert 1 sentence specific to the issue, e.g., updates the database schema for X and linking it to the Y component].

Frontend: Deliver clean, reusable components with responsive layouts, hover/focus states, and semantic HTML.

Backend/Infra: Secure API routes (REST/GraphQL), proper data validation, and clean migrations if required.

Testing & QA: Write unit/integration tests for critical paths and verify breakpoints.

I can start immediately and will share progress updates directly in the PR (complete with screenshots/videos). Ready when you are!

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

[KingFRANKHOOD]

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

Hello, please, I will like to work on this issue

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

[Abidoyesimze]

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

Hi I'd like to work on this issue

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

[Litezy]

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

Please can i work on this?

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

[drips-wave]

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

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

[grantfox-oss]

🦊 GrantFox — @Abidoyesimze has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #420)
2. Your PR will be reviewed by the SO4-Markets maintainers

Good luck! Track your progress on GrantFox.