All Collections
Method Reference Guide
Method FAQ
What is an Action Execution Error?
What is an Action Execution Error?
Understanding Action Execution errors in Method:CRM.
Updated over a week ago

This error mostly occurs on customized screens. In most cases, this error is triggered if data inputted is missing or incorrect. For example:

  • Entering in a name and it's too long (too many characters).

  • A Yes/No field is blank and hasn't been chosen.

  • A field has been blanked out and the screen is trying to process.

For all other cases, when you see this error:

1. Take note of what app you are on, and which screen you are on. The tab name on your browser will indicate which screen you are on. In the below example, the screen name is "New Contact."

2. Expand the link which says More Information to view where the error is exactly occurring. 

3. Take a screenshot of the error.

4. Please contact our service team at or use our chat system. 

If You're Customizing

If you are customizing a screen and you encounter this error, the Action Execution Error dialog box will show you two things:

  • What the error is.

  • Where the error is.

This will help you find the error so you can fix it.

To show this, we will use a custom example of a button which will insert an activity when given a contact:

However, when the button is clicked, this action execution error is generated:

The first part tells us what went wrong:

The Insert/Update Failed, The required field AssignedToRef was either missing or invalid.

  • Insert/Update Failed - Either Insert Records into Table or Update Fields in Table action had a problem.

  • The required field - The problem dealt with a required field.

  • Field AssignedToRef - The name of the field is AssignedToRef.

  • Either missing or invalid - The value given to AssignedToRef was empty or an improper value for that field.

The Action Debug Stack tells us where the error happened.

Note: Unfortunately, the error does not tell us which event the error is in, only the actions. It will be important to note how the error happened. If the error happened because you clicked a button, then the error originates with the button press. However, if the error happened when you enter a screen, then the error is in one of the events of the screen.

In our example, the error occurred when I clicked the Save Activity button, so I will need to customize the screen and go into its Click event. 

The Action Debug Stack will help us pinpoint the error:

  • Line 1 - Conditional: The error is embedded in a conditional.

  • Line 4 - InsertRecord: Since this is the last line in the debug stack, this is where the error occurred.

Now that we know where the error is, we can go into our Insert Records into Table action and see what went wrong!

Did this answer your question?