quick fields agent no summary

replied on December 5, 2016

Can you describe what is making you think that only the post-processing portion of the session is running?

(By the way I'm not able to read your screenshots, they're too small.)

0 0

View 1 previous reply

replied on December 12, 2016

Here is clarification from the user:

Attached are a couple screenshots from the session history.

This session runs every 10 minutes, and grabs files from the repository matching a certain condition. Basically, we’re really just using QF to convert a PDF to a TIF. The post-processing action is to delete the source file. This session usually works fine.

To confirm my suspicions that QF was deleting the source but not creating a new file in its place (at times, again this session usually is fine), I created a workflow that creates an record in a database when a file was created, then had QF run a WF to update a different field for the same record in that database after it was done processing. When you glance at this table, you can tell there’s a lost file due to a failed QF session if there is a NULL value in one of the columns (if it ran successfully, it would have updated the field).

Let me know if you need more information.

1. Failed session, events tab.PNG (25.63 KB)

| Download

2. Failed session, summaries tab.PNG (15.8 KB)

| Download

0 0

replied on December 12, 2016 • Show version history

The first screenshot indicates that it's timing out for inactivity. It's hard to tell why without knowing which documents were being processed but my first guess is that perhaps some of the PDFs are very large and thus it takes a long time to generate pages - this may make the session appear idle when it actually would have finished eventually. Try increasing the inactivity timeout to accommodate longer processing times.

For now, in order to prevent further data loss and so that we have more information if it happens again, I suggest changing the post-processing settings to move to a temporary folder instead of having Quick Fields delete the original documents immediately after capture.

0 0

replied on December 20, 2016

Thanks for that suggestion, my client would like to know how to set the inactivity timeout, thanks!

0 0

replied on December 20, 2016

See this page in the help files:
https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-us/administration/#../Subsystems/QuickFieldsAdmin/Content/Quick-Fields-Agent/Settings-Processing.htm

0 0

Question

Question

Replies

Sign in to reply to this post.