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 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 Square.

Remember to use a dedicated Composer user for the NTO production org in your flow. While the flow is running, use an end user to manipulate data in the NTO production org.

Follow these steps to activate a flow.

  1. Click Edit in the Sync Salesforce Contacts to Square Customers flow.
  2. In 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.
  7. In step 2 of the flow, click the ellipsis icon, and then click Change Connection.
  8. Click the Connection picklist and select Add New HTTP Connection.
  9. Name the connection NTO Square production.
  10. Select Bearer Token as the authorization type, enter the Square production base URL and the Square production access token, and then click Next.
  11. Select Get as the request method, enter the request path for your Square production, and then click Connect. MuleSoft Composer automatically tests the connection. If no error message appears, you have a successful connection.
  12. In step 3 of the flow, click the ellipsis icon, and then select Change Connection.
  13. Click the Connection picklist, select NTO Square production, click Change, and then click Confirm.
  14. In step 4 of the flow, repeat steps 12 and 13 of this procedure, but select the NTO production org connection.
  15. In step 5 of the flow, repeat steps 12 and 13 of this procedure to switch to the NTO Square production connection.
  16. In step 6 of the flow, repeat steps 12 and 13 of this procedure to switch to the NTO production org connection.
  17. Save the flow.
  18. Click Activate. The flow is now running and automatically syncing new or updated contacts in Salesforce with customers in Square.

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 Contacts to Square Customers flow 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 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 Any Status picklist. Here’s an example of some failed instances of the 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 because the HTTP POST method was unable to create a customer using Square APIs. Specifically, United States was entered as the country for the contact in Salesforce, which Square APIs found unacceptable. Square APIs require countries to be in the two-letter format of ISO 3166. To resolve the problem, enter US instead of United States.
    Error information of a failed instance showing a failed HTTP POST using Square APIs.

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 contacts in Salesforce with customers in Square, 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 contacts in Salesforce in sync with customers in Square. Then, you learned about a MuleSoft Composer solution to sync new or updated contacts in Salesforce with customers in Square. 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 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 4 in the first If/Else block and after step 6 in the second If/Else block. In these steps, connect to Slack and notify the appropriate channels that a contact and its corresponding customer are created or updated in Salesforce and Square, respectively. 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

Partagez vos commentaires sur Trailhead dans l'aide Salesforce.

Nous aimerions connaître votre expérience avec Trailhead. Vous pouvez désormais accéder au nouveau formulaire de commentaires à tout moment depuis le site d'aide Salesforce.

En savoir plus Continuer à partager vos commentaires