Troubleshooting
This troubleshooting documentation is designed specifically for application engineers and developers. It provides focused guidance on diagnosing and resolving issues encountered during application and integration of Part Traceability.
|
Troubleshooting details or known limitations that are relevant to end-users or operational procedures are documented separately in the Operations Manual or User Manual. |
Test parts create processing issues
Problem description
There are various Part types which are processed on the production line repeatedly, leading to an excessive number of entries in the quality database. This behavior causes the content of the Part Protocol growing to a size where it cannot be displayed any longer due to a timeout of the browser.
Proposed solution
Ensure that the Part ID for this component is not reused too frequently. Instead, update the Part ID as needed to prevent an excessive accumulation of entries in the quality database.
Default Configuration Scope is erroneously returned
Problem description
When a scope is created via the API and a part telegram is sent to the Data Collector within one second, the caching mechanism (which updates once a second) may inadvertently return the default_config Scope. This issue is most likely to occur in cases where API calls are part of automated tests of modules integrating Part Traceability’s APIs.
Proposed solution
Introduce a delay or verify timestamps to ensure that the cache has been updated before processing the part telegram after the new scope is created.