Troubleshoot

Issue 1

The following error message is displayed when Quickflow is not deployed properly.

Error while deploying Quickflow in one of the machines. For more information, refer the logger console and Troubleshooting section in Quickflow help document.

Possible Causes

• The certificate generated by System Management Server has been used for both Quickflow and AIM.

• The port number is used by other application.

• Connectivity to Message Broker must have failed.

Resolution

• Ensure the AIM certificate and the Quickflow certificate are not same.

• Ensure the port number is not 443 if AIM is installed on the same machine.

• Ensure Message Broker Connection is proper. Refer, Resolving Message Broker Connection below to resolve the connectivity failure.

Resolving Message Broker Connection

• Verify whether the AMQP plugin is enabled. Run the command in the Command Prompt:

  C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.10\sbin>rabbitmq-plugins list

  

• If AMQP plugin is not enabled, run the command:

  C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.10\sbin>rabbitmq-plugins enable rabbitmq_amqp1_0

• Ensure all the listeners are listed in the Configure RabbitMQ Listener Details page. To ensure all the listeners are listed, run the command:

  C:\Program Files\RabbitMQ Server\rabbitmq_server-3.7.10\sbin>rabbitmqctl status

While executing the above commands displays any error like “node unreachable”, follow one of the steps:

• Restart the RabbitMQ windows service.

• Restart the machine where RabbitMQ is installed.

• If none of the above steps resolve the error, repair/reinstall RabbitMQ.

Issue 3

When using datetime values in a Decision activity rule condition, the comparison ignores the time component.

Possible Cause

Due to a limitation in its design, the Decision Activity rule condition lacks support for time comparison in datetime variables.

Resolution

As an alternative, use Rule activity to include both date and time in the comparison.