Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Error Logging Count

I am attempting to log everything to the database and would like to know why the tFlowCatcher sometimes doesn't create a new row when I run the program. It NEVER creates a row when there is a failure and it only sometimes creates a row on success. If it made a row on failure at least the count would show where it was stopped.

0683p000009M8oM.png

The main thing I want is to log somewhere what row my job was at before it failed. I thought the tFlowMeterCatcher would be the easiest way to go about this since it captures and puts the count in an easy spot to do something with. If this is possible to do please let me know how. I just want to send that row that it was last at to a log somewhere. Considering while running this in the application there is a clear indicator for each link exactly how many rows were processed I thought this would be a MUCH easier and straight forward task to accomplish but it clearly is not.
0683p000009M8rF.png

Labels (3)
1 Reply
vapukov
Master II
Master II

Hi,

 

the flowmeter value available after component finishing work

and if you select Die with error in the input component properties this will be not logged into log table

 

but you still can catch this value manually by reading global variables in the tPostJob section:

0683p000009M8vb.png

 

with exactly row number which cause error:

0683p000009M8vg.png

 

tPostJob section will be executed not depending from errors in the main section