Understanding Lean Connect data synchronization failures

 

LeanDNA uses Lean Connect (LC) to synchronize data. Occasionally, issues can arise during this process. This article outlines common Lean Connect failures and how they are addressed.

Understanding Lean Connect failures

Failures occur when there is a problem with how LeanDNA connects to and retrieves data. This can be due to various reasons, such as database connection errors, issues with file sizes, or problems with the server hosting Lean Connect.

Common Lean Connect issues

Database connection errors

This can occur if the server is down, a password has expired, or a user account has been terminated. LeanDNA Support works with your IT team to resolve these issues and restart the data sync.

Dataset not received or no LC message

This can be caused by a downed server, an inactive job user, or changed proxy settings. LeanDNA engineers may need to access the server or collaborate with the IT team to coordinate a shadow session meeting for investigation.

Empty table

This often happens when an important table for planning is missing from the data. LeanDNA Support coordinates with the IT team to ensure the table is available and then restarts the data sync.

File size exceeds limit

If the data file is too large, LeanDNA may need to adjust how the data is extracted. This may involve server access or a shadow session with the IT Team.

Javaheap limit reached

This is related to the memory usage of Lean Connect. LeanDNA may need to adjust settings or filters to resolve this.

How Lean Connect failures are handled

The LeanDNA support team monitors data syncs and investigates any failures. The team uses logs and other tools to identify the specific error and take appropriate steps to resolve it, often working closely with the IT team when necessary.

What to expect

If a Lean Connect failure occurs, LeanDNA will:

  • Identify the specific issue by analyzing logs and system data.
  • Take the necessary steps to resolve the issue, such as adjusting settings, restarting jobs, or coordinating data fixes.
  • Keep you informed and updated about the progress and resolution.

LeanDNA understands the importance of timely data synchronization and is committed to resolving any Lean Connect issues as quickly and efficiently as possible.

Was this article helpful?
0 out of 0 found this helpful
Have more questions?
Submit a request
Share it, if you like it.