#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.

if you do code changes or testing on live server definitely such kind of glitch or feature removed or feature not working issue arise.. otherwise i have not seen another provider face such kind of issue on daily basis and reseller have to report it and client have to face and we reseller do bombard on BS team for quick resolution.

so i do very humble request don't make changes on live server and if you're not doing then find why such kind of issue arise automatically even we reseller don't have access to code.

thanks

Thank you for sharing your concerns.

We completely understand your frustration and sincerely apologize for the inconvenience caused. Please be assured that we do not intentionally perform untested changes directly on the live server. However, in some cases, unexpected issues may still arise due to system updates, third-party dependencies, or edge-case scenarios that only surface in real-time environments.

That said, your feedback is valid, and we take it seriously. We’re already investigating the root cause of the issue and will make sure appropriate safeguards are in place to minimize the risk of such incidents in the future.

We appreciate your continued support and patience as we work toward a more stable experience for all resellers and clients.

Best regards,

Kamrul Hasan