In the Morf dashboard monitoring page, you will be able to see

  • Events (info on events here)
  • Workflow Executions (info on executions here)
  • Issues (more info below)

This page gives you a global view of the activity across all of your workflows.

See demo below of how you can monitor this activity in the Morf dashboard

​
Monitoring Issues

The issues tab will show you a list of warnings (yellow) and errors (red) for a given action/node across your workflows. It will show you how many profiles and workflows have been affected by that issue.

​
Issue classes

We have two classes of issues:

  • Warning: A warning is an indication that something irregular happened, but the action can recover partially and the workflow can continue executing. E.g. if someone enters an invalid phone number, we cannot update their phone number in the CRM, but we can update all of the other properties.
  • Error: An error means that the action could not complete successful and the execution stops.

​
Issue reasons

Issues can happen for a variety of reasons, you will be able to see the details about a given issue by clicking the action step and viewing the error tab. The most common are:

  1. A third party application doesn’t accept the input data, e.g. your Hubspot property “lifecyclestage” does not accept the value from your Formsort form.
  2. A third party application prohibits an action, e.g. we attempted to update a form in Healthie that was already locked.
  3. A profile reconciliation issue, e.g. someone comes through your signup flow with the same email as an existing patient profile. Your workflow is setup to find a contact in your CRM based on email address. The discovered contact ID is already associated to a patient profile, so it cannot be associated to this new lead profile. In order to move forward this person will need to verify their email and the profiles can be merged.

​
Issue resolution

Morf finds and resolves errors during initial implementation and testing. We rely on customers to help test all use cases so that we can identify any configuration issues and resolve before going live.

However, there are some warning and error cases that are expected even after launch. E.g. cases where a third party application doesn’t accept a value that is submitted by a customer in a form, e.g. an invalid phone number.

Or there can be ongoing errors that are expected due to required business logic, e.g. for privacy concerns we won’t merge a lead into a patient without any identity verification, and so an action may fail in order to prevent that from happening.

See here for how Morf monitors.

See demo below of how to monitor issues within the Morf dashboard.

​
FAQ

​
What does the “activity cancelled” warning mean?

This normally occurs if you have reminder workflows configured in Morf. For example appointment or form completion reminders that are configured to wait until a specified time. Most reminder workflows are configured to only allow one execution per “object.” An “object” could be an appointment, a form, a profile. For example, if we receive an appointment updated event that triggers your reminder workflow, and there is already an execution in flight for that appointment, then the first execution will get cancelled and the most recent one will continue, we call this superseding. We emit an “Activity cancelled” warning whenever this happens, but it is benign and does not require any action.