Closed stephanbruijnis closed 2 months ago
This is caused by changes to the Paradym API, both the Workflows and Actions will trigger Webhook events. It needs some further investigation but I think when a connection is created the Workflow didcommConnectionCompleted will be triggered and the API webhook for didcomm.connection.completed. The latter won't have a workflow attached to it and log this error. When upgrading the module to support the new Paradym API we can take care of this (and filter on webhook type)
Issue caused by new events being emitted by Paradym, which contain no workflow information.
New webhook implementation has been solved: https://github.com/Entidad/connector_paradym/issues/9
The microflow Webhook_WorkflowExecutionEvent_Process retrieves Workflow from database on the following xPath:
If not found it logs the following error:
13:39:12 app ERROR Connector_Paradym: Webhook_WorkflowExecutionEvent_Process: no Workflow found for workflowId null and projectId, please check the workflow configuration
Its unclear for which workflow this Webhook with WorkflowExecutionEvent was meant.