Activate, Monitor, and Troubleshoot a Flow

Learning Objectives

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

Activate your flow to automatically sync data in the production environment.
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 production data. First, swap out your existing test connections with newly created production connections, and then activate the flow. Activating the flow enables it to run and perform the expected integration tasks between Salesforce and Jira.

Follow these steps to activate a flow.

Click Edit in the Sync NTO Org Cases with Jira Issues flow.
In step 1 of the flow, click the ellipsis icon, and then click Change Connection.
Click the Connection picklist and select Add New Salesforce Connection.
Name the connection NTO production org, leave the checkbox This is a sandbox organization deselected, and click Create.
Enter your NTO production org’s username and password and click Log In.
Click Allow to grant MuleSoft Composer the permissions. MuleSoft Composer automatically tests the connection. If no error message appears, you have a successful connection.
In step 2 of the flow, click the ellipsis icon, and then select Change Connection.
Click the Connection picklist and select Add New Jira Connection.
Name the connection NTO Jira production, click Create, and then click Accept. MuleSoft Composer automatically tests the connection. If no error message appears, you have a successful connection.
In step 3 of the flow, click the ellipsis icon, and then select Change Connection.
Click the Connection picklist, select NTO production org, click Change, and then click Confirm.
In step 4 of the flow, repeat steps 10 and 11 to switch to the NTO Jira production connection.
Save the flow.
Click Activate. The flow is now running and automatically syncing new or updated customer service cases in Salesforce with issues in Jira.

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 Leads using MuleSoft RPA - Gmail to Salesforce to Slack has an error.

Follow these steps to troubleshoot a flow.

Open your email notification. It looks something like this.
Click the flow name link. MuleSoft Composer is launched, and the flow details page of the flow appears, showing its run history.
If you see one or more failed instances, narrow down the run history to failed instances by selecting Status Failed from the funnel icon (Filter By) picklist. Here’s an example of some failed instances of the Sync Leads using MuleSoft RPA - Gmail to Salesforce to Slack flow.
Click ANY on a failed instance. Its detailed runtime error message appears. In this example, the instance failed because the attachment contained a lot of text but no leads, so the flow didn’t complete running within the specified time. To resolve the problem, look at the time of the failure, identify the emails sent around that time, and then resend the emails. Remember your flow is designed to handle leads that exist in Sales Cloud.

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 new or updated customer service cases in Salesforce with issues in Jira, 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 new or updated customer service cases in Salesforce in sync with issues in Jira. Then you learned about a MuleSoft Composer solution to sync new or updated customer service cases in Salesforce with issues in Jira. 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’re able to implement the flow by following the steps in this module in your own environment, consider deleting any training examples and data you’ve created.

Take It Further

If NTO employees use Slack to communicate and collaborate, enhance the flow described in this module by creating and configuring two more action steps: after step 3 in the If branch of the If/Else block and after step 4 in the Else branch. In these steps, connect to Slack and notify the engineering team that an issue has been created or updated in Jira and should be triaged. 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.