I Created an “Undo Send” Challenge… And the Message Still Got Sent 😬

I Created an “Undo Send” Challenge… And the Message Still Got Sent 😬

# vibecodearena# hackerearth# ai# webdev
I Created an “Undo Send” Challenge… And the Message Still Got Sent 😬Md Mijanur Molla

You 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 Problem

The logic sounds simple:

  • User sends message
  • System delays delivery for a few seconds
  • User can click Undo before it sends

Looks perfect.

But there’s a hidden problem.


⚠️ What Can Go Wrong?

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.


😂 This Is Funny…

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.


🧠 What I Observed

When exploring this challenge:

  • Basic solutions added delay
  • Some added undo flag
  • Many ignored race conditions
  • Very few handled cancellation safely

The code works.

But under timing pressure?

It breaks.


🔍 The Real Issue

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.


💡 What a Better System Needs

A proper Undo Send system should use:

  • Delayed job queue
  • Cancellation tokens
  • Job invalidation before execution
  • Reliable scheduler checks

This ensures:

👉 Undo actually undoes.

And saves lives. 😅


🔥 Try My Challenge

I turned this into a challenge because it mixes:

  • Real engineering
  • Timing bugs
  • And emotional damage

👉 Try it here:
https://vibecodearena.ai/duel/cf2fd567-b2c4-4518-8118-0f839691f685

Can you:

  • Fix fake Undo Send?
  • Prevent accidental delivery?
  • Build a reliable delayed-send system?

🎯 Final Thought

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? 😅