Timeout / 'No Rider Found' orders remain visible and acceptable in Job Radar

Reported by client (Mr. Eamin, DineBD CEO) via WhatsApp, 3 Jul 2026. Evidence: WhatsApp export "Rider App Bugs" — IMG-20260703-WA0006.jpg (order with red "Timeout" badge and a "retry" row in Job Radar), IMG-20260703-WA0009.jpg (order labelled "No Rider Found" still showing an active Accept button).

What to build

Dead orders remain visible and actionable in the rider's Job Radar:

• Orders that timed out still appear with a Timeout badge ("no point showing time out order in Rider job section").
• Orders in No Rider Found state still render an Accept button; the client expects them to transition to timeout/removed.

Timed-out and no-rider-found orders should be excluded from the Job Radar feed (or made non-actionable), and accepting a stale order must be rejected cleanly server-side.

Acceptance criteria

• [ ] Timed-out orders no longer appear in Job Radar
• [ ] "No Rider Found" orders are not acceptable from the radar (no Accept button / server rejects with a clear message)
• [ ] Order state transitions (searching → no-rider-found → timeout) reflected consistently in the radar feed

Blocked by

None - can start immediately

Evidence

Open image in new tab

Open image in new tab