#2015-NEW BROADCAST ERROR :@

[BUG REPORT] SQL Error 1205 – Lock wait timeout exceeded when scheduling WhatsApp broadcast

Hello team,

I'm reporting yet another critical error that occurred while trying to schedule a WhatsApp broadcast.

SQLSTATE[HY000]: General error: 1205 Lock wait timeout exceeded; try restarting transaction

🔍 Context:

This happened during a bulk insert into the broadcast_whatsapp_campaign_sends table, while scheduling messages for multiple subscribers.

❗️This is unacceptable:

I’m honestly tired of running into constant bugs and errors in the system. We rely on BotSailor for client communication and automation, and this is a paid service — not a cheap one. These issues directly affect our operations and reputation.

🧠 Technical explanation:

This specific SQL error means the system was waiting for a database lock to be released (likely due to another process writing to the same table), but it took too long, so MySQL aborted the transaction.

⚠️ Suggestions:Add retry logic for failed inserts.Optimize concurrency handling during broadcasts.Allow smaller batch inserts or staggered processing.Investigate long-running locks or add proper indexing.Provide visibility/logs for partial broadcast failures.✅ What we expect:

That messages are reliably scheduled without critical errors. Period.

Looking forward to a real fix — not another workaround.

Thanks.

Dear User,

We sincerely apologize for any inconvenience caused. There was a glitch, but we have now resolved the issue.

Thank you for your patience and understanding.