**Disclaimer: These are compilations of error and resolutions based on my observation and experience. If they are any other different errors or other methods to resolve them, feel free to add them to in the comments.**

One challenge I faced when I started my PowerApps journey is understanding errors and how to solve them. So I thought I would do a write up that would hopefully be useful to new Power-Appers to identify and solve errors when making apps.

Let’s start with what to do when you seen red indicators (errors) on your PowerApps screen.

**1.Firstly, don’t panic!**

They might be 1 or 10 errors on your screen but all of it could be caused by only one or two glitches in your formulas.

2. **AppChecker is your best friend!,**

It is the ‘plug’ symbol on the right hand corner of the PowerApps builder. If there is a red dot on your App Checker it means they are one or more error somewhere on your form.

**3. Open the App Checker.**

Expand the Errors section in the App Checker to see the list of error summary and on which form the errors occur. If you click on it, it will direct you to the affected formula and it will be underlined by a ‘red worm’

From the screenshot above, you can see that there are 16 errors are on Penguin Land form and my first error is related to the formula** Set(lost,2x,LostItem2,x); **(with red worms underneath it). From here we know that the error could be on that formula or the one before it depending on the error message.

4. **Again, don’t panic** and feel intimidated if you see massive amounts of errors. Because all the formulas are related to one another, solving first few of it will resolve all the other errors.

**5. Work on your errors using Top – Down approach**

Always start work from the first error in the list. Normally the errors in the bottom is related to the ones above so it might be resolved once the above one is fix.

**6. Read the error details**

To get more information on the error, click on the arrow beside the error. The arrow appears only when you hover over the error. The error description will normally give you a better idea on how to solve the problem.

Now that you know where to find the errors, let’s look at some of the errors and their causes and resolutions. From my experience, below are some of the common errors that can be easily avoided and resolved

**Cause:**Syntax error – Missing brackets “()” or curly brackets “{}”.

**Resolution:** Everything open brackets or curly brackets must be closed. Easiest way is to count the number of open brackets and close brackets. They must be equal number

2. **Cause **– Syntax error – Missing operators. Example, a “;” or “&&” is missing from a formula when it is required.

**Resolution:** Be aware of the syntax. Always remember to put “;” at the end of every formula unless it is the last formula for that particular function. (eg: On Select)

4. **Cause:** The required number of parameters in the called function is not met. It could also cause my missing operator that separates the input of the function.

**Example: **

*Set(startTimerItemsAppear).*This is an issue because Set function expects 2 argument but because the “,” is missing, the system reads it as one instead of 2. The correct formula would be

*Set(startTimerItemsAppear,3)*

The detailed error will inform how many arguments is required for that affected formula.

**Resolution**: As you enter your formula into the Formula bar, PowerApps will tell you the inputs of the function. Another way is to refer to the PowerApps Bible for the required or optional inputs of a function.

5. **Cause: **The variable used in a formula (except Set() and UpdateContext()) has not being declared

**Resolution:** I always like to declare the parameters or variables on the Visible function of either the First Screen or affected screen. Depending on the purpose, use either Set() or UpdateContext() to declare a variable.

Now that’s all for now. I hope it will handy for new Power-Appers to find and resolve any issues in your formulas.

Happy Power-Apping 🙂

Came to read this article but a fair few of the images are not showing any more? Even without them though, this article rocks!