Skip to main content
TrailblazerDX, the ultimate AI learning event is heading back to San Francisco March 6-7, 2024. Register Now and save 35% with code T24DEYE424.

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 each of your existing test connections with a newly created production connection, and then activate the flow. Activating the flow enables it to run and perform the expected integration tasks between Salesforce and NetSuite.

Follow these steps to activate a flow.

  1. Click Edit in the Sync Salesforce Opportunities to NetSuite Sales Orders flow.
  2. In step 1 of the flow, click the ellipsis icon, and then select 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.
  7. In step 2 of the flow, click the ellipsis icon, and then select Change Connection.
  8. Click the Connection picklist, select NTO production org, click Change, and then click Confirm.
  9. In step 3 of the flow, repeat steps 7 and 8 of this procedure to select the NTO production org connection.
  10. In step 4 of the flow, click the ellipsis icon, and then select Change Connection.
  11. Click the Connection picklist and select Add New NetSuite Connection.
  12. Configure the connection to your NetSuite production data, and then click Create. MuleSoft Composer automatically tests the connection. If no error message appears, you have a successful connection.
  13. In step 5 of the flow, repeat steps 7 and 8 of this procedure to select the NTO production org connection.
  14. Save the flow.
  15. Click Activate. The flow is now running and automatically syncing new or updated closed-won opportunities in Salesforce with sales orders in NetSuite.

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 the running Sync Salesforce Opportunities to NetSuite Sales Orders flow has errors.

Follow these steps to troubleshoot a flow.

  1. Open your email notification. It looks something like this.
    Email notification about failed instances of a flow.
  2. Click the flow name link. MuleSoft Composer launches, 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 funnel icon (Filter By) picklist. Here’s an example of some failed instances of the Sync Salesforce Opportunities to NetSuite Sales Orders flow.
    Run history of a flow showing Id, Start Date, End Date, Status, and error information of three failed instances.
  4. Click ANY on a failed instance. Its detailed runtime error message appears. In this example, the instance failed in NetSuite because the Salesforce product code, DES00002, doesn’t match its associated NetSuite line item’s internal ID. Remember in unit 1, for this use case we assume that every product in Salesforce has a corresponding line item in NetSuite, and its product code matches the line item’s internal ID. To resolve the problem, replace the product code with its associated line item’s internal ID.
    Error information of a failed instance showing an invalid Salesforce opportunity product’s product code was passed to NetSuite.

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 closed-won opportunities in Salesforce with sales orders in NetSuite, 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 closed-won opportunities in Salesforce in sync with sales orders in NetSuite. Then, you learned about a MuleSoft Composer solution to sync new or updated closed-won opportunities in Salesforce with sales orders in NetSuite. 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.

Note

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 another action step after step 5. In this step, connect to Slack and notify the appropriate channel that an opportunity is created or updated and marked as closed won in Salesforce and its corresponding sales order containing associated line items is created in NetSuite. 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.

Resources 

Keep learning for
free!
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