Sometimes, task execution can be blocked and messages in RabbitMQ can be piled up.
A few examples are,

1. Jiffy Core Application Process may be hung or down due to resource utilization on the server.
2. RabbitMQ crash
3. Bot Issue.
4. DB (Postgres/Mongo) Issue.

Steps to perform during Application Hung

1. Run the Random number from Design and Execution, and see if it’s running successfully or not. If the task is not completed, this confirms that there is an issue with the Core Server process/es.
2. Check for the RabbitMQ queues, and if the consumers are available or not for all the respective queues. Click on the particular Queue and check the Consumer Count.
3. If one or more queues do not have consumers, restart the Jiffy Core application without purging the queues. Consumers will then be available for pickup and processing.

Processes are running, and consumers are available but the messages are not processed by the bot

• This causes the messages to be piled up in Service request queue. Here, messages are selected and do not hit the bot.
• In this scenario, analyse the logs, Bot logs (C:\jiffyservice\logs\JPipeClient), jiffy service logs (C:\Users{Username}\jiffy\logs) for any issue (exception/error).
• Possible solution:
  • Bot restart to restore the functionality.
  • During this time, if the bot may be busy doing some execution, the bot will be unable to complete that execution for that task.
  • That task needs to be terminated from the front end to let the bot execute the next task.