Workflow orchestration is a critical component of R2R, managed by Hatchet. When orchestration failures occur, they can disrupt the entire data processing pipeline. This guide will help you identify and resolve common issues.
First, ensure that the Hatchet service is running properly:
Look for containers with names like hatchet-engine
, hatchet-api
, and hatchet-rabbitmq
.
View the logs for the Hatchet engine:
Look for error messages or warnings that might indicate the source of the problem.
Symptom: Hatchet logs show connection errors to RabbitMQ.
Solution:
Symptom: Errors in Hatchet logs related to database connections.
Solution:
Symptom: Specific workflows fail to start or execute properly.
Solution:
Symptom: Workflows start but fail due to timeout or resource exhaustion.
Solution:
Symptom: Unexpected errors after updating R2R or Hatchet.
Solution:
Use the Hatchet API to get more details about workflow executions:
curl
to query the API (replace <container-id>
with the actual ID):
If you have the Hatchet dashboard set up:
http://localhost:8002
if using default ports).Inspect RabbitMQ queues to check for message backlogs or routing issues:
http://localhost:15672
).Symptom: Documents fail to process through the ingestion workflow.
Solution:
Symptom: Vector store (Postgres with pgvector) not updating correctly.
Solution:
If you’re still experiencing issues after trying these solutions:
Remember to provide:
r2r version
)By following this guide, you should be able to diagnose and resolve most workflow orchestration issues in R2R. If problems persist, don’t hesitate to seek help from the R2R community or support channels.
Workflow orchestration is a critical component of R2R, managed by Hatchet. When orchestration failures occur, they can disrupt the entire data processing pipeline. This guide will help you identify and resolve common issues.
First, ensure that the Hatchet service is running properly:
Look for containers with names like hatchet-engine
, hatchet-api
, and hatchet-rabbitmq
.
View the logs for the Hatchet engine:
Look for error messages or warnings that might indicate the source of the problem.
Symptom: Hatchet logs show connection errors to RabbitMQ.
Solution:
Symptom: Errors in Hatchet logs related to database connections.
Solution:
Symptom: Specific workflows fail to start or execute properly.
Solution:
Symptom: Workflows start but fail due to timeout or resource exhaustion.
Solution:
Symptom: Unexpected errors after updating R2R or Hatchet.
Solution:
Use the Hatchet API to get more details about workflow executions:
curl
to query the API (replace <container-id>
with the actual ID):
If you have the Hatchet dashboard set up:
http://localhost:8002
if using default ports).Inspect RabbitMQ queues to check for message backlogs or routing issues:
http://localhost:15672
).Symptom: Documents fail to process through the ingestion workflow.
Solution:
Symptom: Vector store (Postgres with pgvector) not updating correctly.
Solution:
If you’re still experiencing issues after trying these solutions:
Remember to provide:
r2r version
)By following this guide, you should be able to diagnose and resolve most workflow orchestration issues in R2R. If problems persist, don’t hesitate to seek help from the R2R community or support channels.