Debugging application in Anypoint Studio

Join us to learn about Debugging application in MuleSoft Anypoint Studio. We will talk about flow, Attribute and variables. Also learn about step by step process to use logger in Mulesoft.

Debugging application in Anypoint Studio

YouTube video


Used to call a sub-flow/private flow. Mandatory Config Details required: flow name to be called. All names are present in drop-down list. Default : empty but it fails to deploy if you don’t give any flow name from drop down.


We know that attributes is part of Mule Message. Attributes are nothing but the meta-data coming from the system which we are connecting. Accessed as #[attributes.requestPath] #[]. Attributes are replaced with new or no values whenever we connect to any external systems.


Mule 4 has only one kind of variable called “variable” where in Mule 3 we used to have 3 kinds of variables (flow, session and record). They are used to preserve information which you think might be useful at any point of flow. Accessed as #[]. Vars are carried as long as the flow is connected. If you think that you no longer need the variable, you can use “remove variable” to remove it.


Mandatory Config Details required: Nothing is mandatory here. You can set anything in “message” field.


Checkout our complete MuleSoft Training to learn all about MuleSoft. We have 15+ session for you with Final Project.

Amit Chaudhary
Amit Chaudhary

Amit Chaudhary is Salesforce Application & System Architect and working on Salesforce Platform since 2010. He is Salesforce MVP since 2017 and have 17 Salesforce Certificates.

He is a active blogger and founder of Apex Hours.

Articles: 460

Leave a Reply

Your email address will not be published. Required fields are marked *