looking through other posts, I have not found a solution to our issue
we are having an issue with task notifications not being sent, although we can verify assignment in K2 Management (workflow). we are running the latest release of K2 Five (5.3)
an email action has been added to the workflow to confirm it's running, and the recipient is identical to the task action assign to.
here is the configuration
Best answer by lkimberly
Hi @ltjwstl ,
This is likely due to the mismatch of values like you mentioned. Can you update the sendmailfrom so that it reflects the email address of the K2 service account set in the system self node? After that, restart the K2 service and test if task notifications are working.
Cheers,
Kimberly
K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member.
Do you have HostServer logs from when the email should have sent? (These are typically located in [INSTALLDIR]K2Host Serverin) If so, are there any error messages in the logs?
If there are no errors in the HostServer logs, are task notifications sending from other processes? If there are no other processes with task notifications, and there are no errors in the logs, can you check the EventBus.ClientRecorderError table in the K2 database and see if there are any entries that correspond with the time the task notifications should have sent?
looking through the log, this error is occurring each time the workflow is being executed
"270232168","20*personal details removed*:51:13","Error","MessageBus","61007","SendMessageException","MessageBusRuntime","61007 Permanent failure sending message : System.Exception: No destinations could send the message . at SourceCode.MessageBus.Server.MessageBusRuntime.SourceCode.MessageBus.IMessageDestination.Send(String title, MessageExtendedInformation extended, IEnumerable`1 attachments, MessageBodyReader[] messageBodies)","","","NY-K2Test1:C:Program FilesK2Host ServerBin","270232168","a55de56cb3bb480a8d2d59d1fed6d26a","" "270232204","20*personal details removed*:51:15","Error","General","24148","UMEmptyQError","K2DestQueue.RunDestQueue","24148 The User Manager 127.0.0.1 returned an empty queue with name K2_Test.","anonymous","0.0.0.0","NY-K2Test1:C:Program FilesK2Host ServerBin","270232204","0263bde084a244838a2ad9f44178e493",""
looking at the following knowledge article, I noted the values are not matching as suggested. the service account is not associated with the email account.
This is likely due to the mismatch of values like you mentioned. Can you update the sendmailfrom so that it reflects the email address of the K2 service account set in the system self node? After that, restart the K2 service and test if task notifications are working.
Cheers,
Kimberly
K2 will not accept any liability for any issues arising from actions taken in respect of the information provided by any forum member.
Can you please confirm that you have the correct mail server set as 'Default' in the server's corresponding Environment Library? Please see this KB https://help.k2.com/support-services/kbt171668.
Could you share some details on the error that you saw in the Hostserver log? If the Send Task Notification starts in K2 then it will have the following events in the log, see sample below.
-----------------------
"Info","EventBus","7019","Processing","EventQueueProcessing.Process","7019 Processing event instance with ID: some_id“ "Info","EventBus","7006","Processing","EventQueueProcessing.ExecuteAssembly","7006 Function executed successfully“
It seems that there is a problem in the workflow itself because if you reset the recipient to the originator you should be able to received notification.
- please check the work flow itself if there's an error - K2 Management site > Workflow servers > Instances > Click the VIEW FLOW. (you should be able to see where the exact error occurred. - If you will customized the recipients you should use the K2 FQN email format to work FQN i believe starts with K2. example (K2:ABCdabuskol) - another one, as per your posting error, it seems that the destination is empty. If you use role/group as recipients there should be a valid email.