Adeptia Cloud (4.x) Issues and Diagnostics

• Category

AC4_Application

License error on Process flow execution

License 15 days trial periods exceed

All the pod's logs indicate a license error.

1. Verify the status of the pods to determine if they are running.

2. Review the logs for comprehensive error details.

AC4_Application

All REST providers are experiencing failures.

java.lang.RuntimeException: The resource Cache Cache is not alive (STATUS_SHUTDOWN): Error while adding an object in the application cache. [Cache Name=resourceCache]

1. When you open any custom workflow of the client or run, this error will occur.

1. Check the runtime and Webrunner pod logs for a detailed error analysis.

AC4_Application

Process Description context variable changes in Adeptia Connect while it displays the correct variable in AIS.

The variable name for the process flow description has been modified in AC4. Therefore, any value assigned to this variable will not be displayed on the Dashboard.

1. When the user sets or overrides the process flow description in the process flow, it will not populate after execution..

1. Verify this independently in the AIS and AC environments.

2. Evaluate the process flow description variable's value within the context of AIS and AC individually.

AC4_Application

Target file creating with zero kb

After migrating the JMS-based process flow from AIS to AC 3.x, a process flow is implemented where the custom plugin utilizes the most recent dom4j jar from the AC 3.x product version. Subsequently, the process flow runs successfully, generating a target file of zero kilobytes and the Runtime logs indicate the following error:

Caused by: java.lang.ClassNotFoundException: org.jaxen.VariableContext

1. The process flow executes successfully on both AIS and AC 3.x platforms.

2. In AIS, the process flow generates the expected output file, while in AC 3.x, an output file with zero kilobytes is produced without any modifications to the process flow or related objects.

1. Verify the execution process flow for AIS and AC 3.x separately.

2. Examine the runtime and webrunner logs.

AC4_Application

While activating the transaction, the following error was encountered:

Error occurred during the activation of the event, specifically in obtaining the database row lock due to SQL syntax issues.

500 internal server error occurred during the activation of a transaction. An SQL syntax error is triggered due to a database row lock specific to the MySQL server version.

1. Check the MySQL database-related properties and ensure their values match those in value.yaml from Adeptia documentation.

AC4_Application

Transaction getting in a queued state

1. Specific transactions are being queued in the AC4 Application.

1. After enabling the event, the transaction became stuck in the queue state.

1. Verify the event properties or settings.

2. Disable the event and then re-enable it to observe its behavior.

AC4_Application

1. All transaction and process flows are being queued for processing.

1. After enabling the event, the transaction is stuck in the queue state.

1. Validate the Event properties or settings.

2. Deactivate the event and subsequently reactivate it to observe the behavior.

3. Examine the Runtime Pod Logs for a thorough analysis of any errors encountered.

AC4_Application

Error encountered while utilizing the Code Repository for enabling Versioning.

After configuring versioning following Adeptia documentation, an error is displayed on Adeptia Application environments.

Error Message: Unable to find reference of HEAD/master: The requested repository does not exist, or you do not have permission to access it.

1. An error occurs when checking in or checking out any activity in the application.

2. The environment experiences slowness after enabling versioning.

1. Please review the Webrunner logs for a comprehensive error analysis.

2. Align the Version Control settings with the Azure directory for consistency.

AC4_Application

The unpublished process flow does not display the "Publish as a template" option.

Hackbarth has reported an issue where the unpublished process flow does not display the "Publish as a template" option, as illustrated below, along with the screenshot provided by the client.
Product Version: 4.3.04.

Business user not able to use Publish as template option for unpublish process flow after upgrade 4.2.6.3 to 4.3.04

Compare both v4.2.6.3 and v4.3.04 unpublish process flow properties
Compare the License permission and version for both versions

AC4_Infra

Elasticsearch environment is not accessible

the elasticsearch environment for paychex client is not accessible due to below error
"Caused by: java.lang.IllegalArgumentException: node settings must not contain any index level settings",

When user try to login using EFK application link , it will not able to login with error.

1. Check the logs in EFK Pod for detail error.

2. Check the login credentials with MST

3. If there is an error then check internally with Team member about the error.

4. Check the EFK documentation , if there is anything given regarding the error

AC4_Infra

Instruction to find Public IP of AC Cloud customer environments in Azure.

Find the AKS external id

NA

NA

AC4_Infra

AC Cloud Upgrade Error Handling

How to handle specific issue while upgrading AC Cloud Version 4.2 to 4.3.04

1. Upgrade failed while performing helm upgrade command

2. Error regarding HA mode and replicas stateful configuration

1. Execute the helm command in debug mode to capture complete error

2. Check internally with team member if anyone get before such error

3. Report to Product support team and work on the resolution with Product and product support team.

AC4_Infra

Veloro Backup Failure for Persistence Volume

Backup failed / Restic lock issue for velero backup

1. Backup will not be complete of that day , show the error at lense

1. Check the velero pods logs for detail error

AC4_Infra

AC4 Microservice CPU scaling

For AC4 customers if we are increasing the cpu of microservices then in that case we have to update the "readiness.probe.cpu.threshold" also of that microservice.

1. CPU increased for large data processing and consume the limits

1. Check the CPU performance in lens at runtime

AC4_General

How to clean up the queued processes from both the rabbit MQ and database

Process and Transaction stuck in queue state

After triggering the process flow and transaction stuck as queue state in the application dashboard.

1. Check the rabbitmq gui , Is there any queue is showing or not.

2. Check the runtime logs , if there is any error presents.

3. turn off the transaction and turn on again to check the behaviour

4. Enable the trigger in sequence in the event

AC4_General

Online tool to analyze the heap dump

After taking the heapdump , team can use online tool to read the statistics

NA

NA

AC4_General

SQl query to Fetch Transaction Name from Event Registry Table

There is no direct relationship between event and Transaction table so MSt creates an Join query to fetch this information

NA

NA

AC4_General

Verbose Logs in FTP Source and Target

How to enable verbose logs in FTP objects and where you can find those logs in AC 4

NA

NA

AC4_General

steps for generating and applying the PGP key for encryption or decryption

detailed process and steps to generate and apply PGP key in AC4

NA

NA

AC4_Application

Process flow issue

Concurrency is set to 10 but only 1 process flow is running at a time. 

Even after disabling the trigger in Sequence option only 1 flow is getting executing at a time

Check the transaction log DB and verify for any stuck transactions? There have been scenarios where the actual status in backend and UI may not be same. Check for any orphan transactions in backend.