When Your Bot "Reads Without Replying" or Even "Doesn't Read at All"

Congratulations! If you've followed the previous chapters to this point, you've successfully deployed an intelligent AI bot to serve your needs. You've probably already shown off your creation in family and friend group chats.

However, in the real business world, software can never be permanently flawless.
One morning, while you're frying an egg pancake, a customer suddenly says: "Boss, your Line bot is broken! I sent it messages, but it's ignoring me!"

At this moment, as a Vibe Coder, you mustn't panic and Google "What to do when Line Bot breaks."
You need to learn to act like a doctor—through a few simple "diagnostic steps"—to accurately pinpoint the issue, then hand the medical chart to AI to prescribe the solution!

---

Diagnostic Step 1: Check the Webhook Status in LINE's Official Dashboard

The prime suspect when a bot ignores users is usually: "The signal isn't even reaching your server."

1. Log in to the Line Developer Console.
2. Navigate to your Provider -> Select your Channel -> Click the Messaging API tab.
3. Scroll down to the Webhook settings section.
4. Click the Verify button.

At this point, Line will attempt to throw a virtual baseball to your server.

• If it shows Success (green text): Congrats! Your network connection is fully functional. The issue must lie in your code logic (proceed to Diagnostic Step 2).
• If it shows Error (red text): This means Line's ball can't reach your server. Possible causes include:
  • Your server (e.g., Ngrok, Vercel, Render) is shut down or crashed.
  • Your Webhook URL is incorrect (e.g., forgot to add /callback, or used http instead of https).
  • Your server's firewall is blocking Line's connection.

---

Diagnostic Step 2: Check the Server Logs (Error Logs)

If the Webhook connection is fine, why is the bot still unresponsive? Now we need to check the "medical records" (Logs).

No matter where your server is hosted, there will always be a window displaying logs. If you're developing locally, this is the Terminal window below your Cursor.

In the logs, you might see a long string of red text—this is the system sending an SOS. Common fatal errors include:

1. Validation Failed: Signature validation failed

This usually happens when you've just created the project. To ensure messages are genuinely from Line and not forged by hackers, Line requires signature verification.
Root Cause: Your .env file has an incorrect or missing LINE_CHANNEL_SECRET.

2. Reply Failed: Invalid reply token

This is a very common commercial-grade bug.
Root Cause: Line's rule is that when a user sends you a message, it provides a replyToken (reply token). You must use this token to exchange for one free reply to the user. However! This token has an "extremely short lifespan (usually just minutes)" and can only be used once!
If your code accidentally calls client.replyMessage() twice, the second attempt will fail with this red error because the token has expired.

3. OpenAI Quota Exhausted: 429 Too Many Requests or Insufficient Quota

If your bot sometimes replies and sometimes doesn't, and you see OpenAI-related red text in the logs:
Root Cause: Your OpenAI API account has "run out of credits," or you're making requests too frequently and have been temporarily blocked by OpenAI's system. Immediately log in to OpenAI's dashboard to bind a credit card and top up!

---

The Ultimate Vibe Debugging Move: Feed the Red Text Directly to AI!

In the past, engineers encountering errors would copy the red text to Google, then sift through dozens of English forum posts on StackOverflow to find a solution—a half-day ordeal.

Now, you just need to master the most brute-force debugging spell:

【Ultimate Red Text Debugging Prompt】
I'm developing a Line Bot, but my Node.js terminal shows the following red error:
[Copy and paste the entire red error text from your terminal here, including the stack trace verbatim]

Please refer to my current @app.js code.
What is the exact cause of this error? How should I modify the code to fix it? Provide the complete corrected code directly.

Once you send this spell to Cursor's AI, it acts like an X-ray machine—instantly spotting missing brackets or flawed logic in your code—then serves the "fixed code" right to your lips.

Just click Accept, restart the server, and voilà! Your bot will be cheerfully greeting customers with "Good morning, handsome!" again.

---

Conclusion: You Now Have the Power to Change the World

Through these 5 chapters of Line Bot training, you've completed the full business journey—from "no-code graphical menu setup" to "implanting an AI brain to become a super salesperson."

More importantly, you've learned not to fear errors, because you know that pasting logs to AI can solve any problem.
With this Vibe Coding capability, whether it's a breakfast shop, real estate agency, nail salon, or even your own startup idea, you can turn concepts into revenue-generating products in a single weekend.

Keep exploring our advanced courses! Which industry will you disrupt next?

Chapter Summary

• Understand core concepts and principles
• Master implementation methods and techniques
• Familiar with common issues and solutions
• Able to apply in real projects

Further Reading

• Official documentation and API references
• Open source examples on GitHub
• Technical books and online courses
• Community discussions and tech blogs

Implementation Example

Basic Example

# This section provides a complete implementation example

Steps

1. Setup: Configure development environment
2. Data: Prepare required data
3. Implementation: Build core functionality
4. Testing: Verify correctness
5. Optimization: Improve performance

Common Errors

| Error Type | Cause | Solution | |------------|-------|----------| | Compilation | Syntax | Check code syntax | | Runtime | Environment | Verify dependencies installed | | Logic | Algorithm | Step-by-step debugging | | Performance | Efficiency | Use profilers |

Code Example

import sys

def main():
    print("Hello, World!")

if __name__ == "__main__":
    main()

References

• Official documentation
• API reference
• Open source examples
• Community discussions