This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Jul 18, 2018, 7:02 PM
5 Posts

Agent "After new mail has arrives" doesn't see the new document

  • Category: Application Development
  • Platform: Windows
  • Release: 9.0.1
  • Role: Developer
  • Tags:
  • Replies: 4

In an agent with "After new mail has arrived" doesn't recognize the new document.
===================
...
...
Set db = session.CurrentDatabase
Set docParam = db.GetProfileDocument( "Parametres" )
Call agentLog.OpenAgentLog
Call agentLog.LogAction( "Start of the agent: " + CStr( Time ) + " on " + CStr( Date ) + "." )

agentLog.LogActions = True
'Get the new emails...
Set collection = db.UnprocessedDocuments
Set memo = collection.GetFirstDocument()

While Not ( memo Is Nothing )
'... never goes here
Call agentLog.LogAction( "Valid Pricing List Email: " + InDocParam.ValidPricingListEmail(0))

...
...
Wend

Call agentLog.LogAction( "End of agent: " + CStr( Time ) + " on " + CStr( Date ) + "." )
...
=======================
In my log I only have the Start and End of agent info.

I also tested "Before new mail arives" and I got the same issue.

 

I made a compact and Fixup without change
any sugg.?


Regards

Jul 18, 2018, 8:33 PM
323 Posts
Anything in log.nsf?

I can't tell exactly what's happening with a particular document.

I also don't see any error handling, so you'd need to check in the log.nsf at the particular time the agent ran to see if there are error messages.

Does the agent *ever* process *any* document? Has it in the past?

Jul 18, 2018, 8:33 PM
323 Posts
Anything in log.nsf?

I can't tell exactly what's happening with a particular document.

I also don't see any error handling, so you'd need to check in the log.nsf at the particular time the agent ran to see if there are error messages.

Does the agent *ever* process *any* document? Has it in the past?

Jul 24, 2018, 8:51 PM
323 Posts
absent more information ...

... your database may be corrupt. An ID table corruption would cause the agent to miss the relevant document. This would happen to all documents routed to the database, not just one.

Other database corruptions can also cause it.

fixup should identify the issue; however it may destroy the document. So make a file-copy backup of the entire database, save it offline.

Jul 24, 2018, 8:51 PM
323 Posts
absent more information ...

... your database may be corrupt. An ID table corruption would cause the agent to miss the relevant document. This would happen to all documents routed to the database, not just one.

Other database corruptions can also cause it.

fixup should identify the issue; however it may destroy the document. So make a file-copy backup of the entire database, save it offline.


This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal