
Md Mijanur MollaYou know that moment. You send a message. Then instantly realize… 👉 You should NOT have sent...
You know that moment.
You send a message.
Then instantly realize…
👉 You should NOT have sent that.
So you hit Undo at lightning speed.
Relief.
…or so you think.
Now imagine the system says message undone.
But it still gets delivered.
💀
That’s not just embarrassing.
That’s a bug.
So I turned this into a coding challenge on VibeCode Arena.
And honestly…
This one got too real.
The logic sounds simple:
Looks perfect.
But there’s a hidden problem.
In real systems:
• Undo is clicked but send job still executes
• Delayed task was already scheduled
• Cancellation doesn’t stop background process
• Race conditions decide whether message survives
And suddenly:
👉 “Undo” lies.
👉 Message still goes out.
👉 Your panic becomes permanent.
Until you realize it’s a real distributed systems problem.
Because “Undo Send” is not really unsending.
It’s usually:
👉 Delayed sending.
And that changes everything.
When exploring this challenge:
The code works.
But under timing pressure?
It breaks.
This is not just messaging logic.
It’s about:
• Scheduled jobs
• Cancellation logic
• Race conditions
• Reliability under timing conflicts
Because:
👉 “Undo” is meaningless if the send job already escaped.
A proper Undo Send system should use:
This ensures:
👉 Undo actually undoes.
And saves lives. 😅
I turned this into a challenge because it mixes:
👉 Try it here:
https://vibecodearena.ai/duel/cf2fd567-b2c4-4518-8118-0f839691f685
Can you:
Some bugs crash servers.
Some bugs ruin weekends.
This one…
👉 Can ruin relationships. 😭
So tell me 👇
Have you ever trusted “Undo Send” a little too much? 😅