Fails to identifies complete TABLE

[Anonymous]

I have a scenario where the Blueprism fails to identify some of the elements in TABLE (It identifies only first 10 rows out of say 70), when errors logs are enabled. While we enable logging then BP identifies complete table. Is there any logical link between both?  After enabling €˜Error logs only€™ the system performance is slower compared to performance in €˜Enabled logs€™, is there any explanation for this?

[Denis__Dennehy]

I am guessing what you describe is a red herring.  Error logs only is actually doing less than logging fully enabled, so if anything performance would be slightly improved as it is not having to log information to the database.   Make sure you are selecting as few attributes as possible when interfacing with your table and you have Match Index enabled.  

[John__Carter]

As far as I'm aware there is no relation between application manger functionality and logging. if you raise a support ticket then the support team will help you investigate the effect you are seeing.