ROCKETRIDE_COMMON_MISTAKES

RocketRide Common Mistakes & Troubleshooting Guide

A comprehensive guide to avoiding common pitfalls when building RocketRide pipelines and applications.

Last Updated: March 26, 2026

---

Table of Contents

• Pipeline Configuration Mistakes
• SDK Mistakes (Python & TypeScript)
• Blocking the Async Event Loop - CRITICAL
• Language-Specific SDK Mistakes
• Component Configuration Mistakes
• Data Flow Mistakes
• Engine Extension (Python–C++ Interop)
• Quick Reference

---

Pipeline Configuration Mistakes

Mistake 1: Mismatched Response Keys

Problem:

# Pipeline has custom laneName
{'provider': 'response_answers', 'config': {'lanes': [{'laneId': 'answers', 'laneName': 'chat_response'}]}}

# But code expects default key
response = await client.chat(token=token, question=question)
answer = response['answers']  # ERROR: KeyError! Key is 'chat_response'

Why This Happens: The response component's laneName parameter changes the JSON key in the response. When you customize it, your client code must match.

Solution:

# Match your pipeline configuration
answer = response['chat_response']  # CORRECT: Use custom key from pipeline

Better Solution:

# Use default response configuration (no custom lanes)
{
  "provider": "response_answers",
  "config": {}  // CORRECT: Use defaults
}

# Then your code works with standard keys
answer = response['answers']  # CORRECT: Works with default config

Rule: If you customize laneName in your pipeline, you MUST update your client code to match. When in doubt, don't customize - use defaults!

Note: Response components are lane-specific. Use response_answers for answers, response_text for text, response_documents for documents, etc.