Stay informed and check the overall health of LYNQ by using the Systems Insight screen. 

Please wait
Be patient with this screen. It can take a minute or two to run on larger databases.

A great feature used by support when troubleshooting the application at the technical level. 

Don’t forget to backup your databases and put them in your maintenance plans. 

If you see a high number of transactions that have a status of posting this might imply that the application pool settings need to be fine-tuned.  Check out our knowledge base articles on this subject. 

Data is read from
Enterprise Resource Planning using LYNQ’s proprietary views.  Sometimes these views are customised to give you some extra data mapped through to LYNQ.  Be aware that views can get overwritten with an upgrade.  Best to let LYNQ help you perform your upgrade.  You can book us through the support desk.

Platform Service
The LYNQ Platform Windows Service consolidates your activity into transactions.  This service may stop due to heavy load on the server or it failed to start during a server reboot.  Check this service is running on the Web Server.

System Insights displays the current health and state of your LYNQ application.  This page is used by system administrators to troubleshoot and diagnose areas of LYNQ that are not functioning as expected.  The SQL account that is specified in Settings, Database Settings must have SQL admin rights for this page to function properly.

Any values on the page that are highlighted red should be investigated for the continued operational health of LYNQ.  This page provides at a glance a quick way to identify if there are any underlying SQL views that are not functioning correctly due to violation of key constraints.  This is particularly useful when the database of the Enterprise Resource Planning application that LYNQ is connected to is set to a collation that is case sensitive.  LYNQ is not a case sensitive application and therefore SQL views may not execute if there are duplicate keys returned. 

One example of this is where two Product records have been created in the Enterprise Resource Planning application that differ on case.  LYNQ would treat the value PRODUCTA and producta as a duplicated value.  If duplicate keys are returned by the LYNQ SQL views, the application will be severely affected and, in some cases, partly or fully inaccessible by users.  It is therefore important to understand these limitations and monitor the health of the application to ensure the application is fully operational.

Use the System Insights feature for a quick view


Tab Name


No of licensed seats activated vs number of seats purchased

Database Size

Size in MB of the databases used by LYNQ mom

Top Table

The largest table in LYNQ mom by size in MB

Top View

The largest view in LYNQ mom by number of rows


Views that duplicates or errors

Windows Service

Last date and time when the LYNQ Platform service executed

Raw Data

No of raw data records waiting to be processed by the LYNQ Platform service.  A high number of records indicates that the LYNQ Platform service is not running


Status of analytical statistics with option to recalculate.



Number of transactions generated by the timesheet or workbench feature, split by transaction status.

Transactions posting SQL View

Transactions that are approved and waiting to be posted to the ERP application.


Tab Name


List of all proprietary SQL views used by LYNQ.  This tab can be used to identify views which have duplicate key values.  Drill down on the number of duplicates to understand which data is causing issues with the execution of the view


Tab Name


List of all proprietary SQL tables used by LYNQ.  This tab can be used to order tables by size and row count.


Tab Name


Access to different log files generated by LYNQ


Tab Name


A report of all events received via factory automation, Workbench and Actions in LYNQ


Tab Name


A view of current factory automation signals


Related Articles (1)

Comments (0)