Go to Configurator>Mail Services > Notification Server>Common Options>Web Services Invocation Timeout and increase the value. You need to Apply for this to take affect. Note this will restart services so should be done outside of main working hours.
Notify stops scanning a project when it finds a user who needs more messages sent than what the settings specify in SEND AT MOST in the Notify Options. Notify also does not increase the NFYTID field in the trkusr table for that user so that when it scans the database again the next time it sends out the same messages and then quits again. (i.e.
Different SMTP servers handle the length of the e-mail subject line in different ways. In some cases, the text of the subject line becomes unreadable if the number of characters in the subject line exceeds a certain amount. By altering the TS_SYSTEMSETTINGS table in the SBM database, you can try different subject lengths to determine the length at which the subject becomes readable for the version of your e-mail reader .
The complete warning messages from the Event Viewer Application Log is: NOTIFICATION_NAME: ( notification ) context - Unable to read item with id xx from database. And:
The problem is that a sub-relational field has two references: (1) relational field in current table, and (2) sub-field, the field with actual required data which is located in the table:record referenced by relational field. The problem is that notification server reads from db only sub-field and does not read relational field.Thus the relational field value is always zero and it cannot go into other table and continue evaluation of rules.
