Skip to main content

Activate, Monitor, and Troubleshoot a Flow

Learning Objectives 

After completing this unit, you’ll be able to:

  • Activate your flow to automatically sync data.
  • Monitor and troubleshoot your flow.

In this unit, you first learn how to activate your flow in the production environment. Then you learn how to monitor and troubleshoot your flow while it’s running.

Activate a Flow

After you’ve tested the flow to your satisfaction, you’re ready to activate it using your Salesforce production org. Swap out the existing NTO sandbox org connection with a newly created NTO production org connection, and then activate the flow. Activating the flow enables it to run and perform the expected integration tasks between Salesforce and Asana. 

Follow these steps to activate a flow.

  1. Click Edit in the Sync NTO Org Cases with Asana Tasks flow.
  2. Go to step 1 of the flow, click the ellipsis icon, and then click Change Connection.
  3. Click the Connection picklist and select Add New Salesforce Connection.
  4. Name the connection NTO production org, leave the checkbox This is a sandbox organization deselected, and click Create.
  5. Enter your NTO production org’s username and password and click Log In.
  6. Click Allow to grant MuleSoft Composer the permissions. MuleSoft Composer automatically tests the connection. If no error message appears, you have a successful connection to the NTO production org.
  7. Save the flow.
  8. Click Activate. The flow is now running and automatically syncing customer service cases in Salesforce with tasks in Asana.

Now that your flow is active, you learn how to monitor the flow and troubleshoot any problems that arise.

Monitor and Troubleshoot a Flow

After your flow is active, it continues to run in the background. MuleSoft Composer automatically handles where to deploy the flow, how to manage it, and when to scale it for optimal performance. 

If there’s an error with any of the runtime instances of the flow—and assuming MuleSoft Composer is configured for email notifications in your Salesforce org—MuleSoft Composer sends you an email notification. You should monitor your emails for any notifications from MuleSoft Composer. For more information on configuring email notifications, see MuleSoft Composer Installation and Configuration.

Typically, an email notification shows which flow has an error, the number of failed runs out of the total runs, and the start and end time of the report. You should then take steps to troubleshoot the error.

Assume you’ve received an email from MuleSoft Composer notifying you one of your flows called Sync Service Cases with Slack Notifications has an error. 

Follow these steps to troubleshoot a flow.

  1. Open your email notification. It looks something like this.
    Email notification about a failed flow.
  2. Click the flow name link. MuleSoft Composer is launched, and the flow details page of the flow appears, showing its run history.
    Run history of a flow showing Id, Start Date, End Date, and Status of six instances.
  3. If you see one or more failed instances, narrow down the run history to failed instances by selecting Status Failed from the Any Status picklist. Here’s an example of some failed instances of the Sync Service Cases with Slack Notifications flow.
    Run history of a flow showing Id, Start Date, End Date, Status, and error information of three failed instances.
  4. Click CLIENT_ERROR on a failed instance. Its detailed runtime error message appears. In this example, the instance failed because an invalid value was passed to a Slack channel. To resolve the problem, enter a valid value for the Slack channel.
    Error information of a failed instance showing an invalid value was passed to a Slack channel.

Keep in mind that you lose access to MuleSoft Composer when your license expires. So make sure to renew your MuleSoft Composer license before it expires.

Congratulations, you’ve done it! You’ve successfully used MuleSoft Composer to build and run an integration flow that automatically syncs customer service cases in Salesforce with tasks in Asana, thus eliminating the manual tasks and achieving near real-time integration.

Wrap It Up

In this module, you first learned about the challenge of keeping customer service cases in Salesforce in sync with tasks in Asana. Then, you learned about a MuleSoft Composer solution to sync customer service cases in Salesforce with tasks in Asana. Finally, you learned how to use MuleSoft Composer to perform flow creation tasks such as preparing to create a flow, designing and testing a flow, activating a flow, and monitoring and troubleshooting a flow.


The examples and data presented in this module are purely for training purposes. If you have been able to implement the flow by following the steps in this module in your own environment, consider deleting any training examples and data you have created.

Take It Further

If NTO employees use Slack to communicate and collaborate, enhance the flow described in this module by creating and configuring another step at the end of the If and Else branches of the flow. In each of these steps, connect to Slack and notify the appropriate channels that a task has been created in Asana. To learn how to use Slack in a flow, take Slack Automation with MuleSoft Composer.

To get step-by-step instructions to solve other common integration problems using MuleSoft Composer, take the other modules in the MuleSoft Composer Trailmix.


Keep learning for
Sign up for an account to continue.
What’s in it for you?
  • Get personalized recommendations for your career goals
  • Practice your skills with hands-on challenges and quizzes
  • Track and share your progress with employers
  • Connect to mentorship and career opportunities