MESA Docs
MESA Homepage
  • Welcome to MESA
    • Installing MESA
    • Dashboard
    • Core Concepts
    • Getting Help
  • Templates
    • Template Library
    • Installing & Editing
  • Workflow Builder
    • Triggers
    • Actions
    • Fields
      • Variables
      • Formatting Variables
      • Liquid Templating
    • Testing
  • Workflow Activity
    • Tasks
      • Troubleshooting
      • Replay
    • Logs
    • Time Travel
  • Best Practices
    • Set Titles & Descriptions
    • Track Time Saved
    • Enable Failure Notifications
    • Avoid Infinite Loops
  • Going Further
    • Plans & Billing
    • Notifications
    • Credentials
    • Understanding the Queue
    • Export & Import Workflows
    • Platform Thresholds & Limits
  • Built-in Tools
    • Activity Log
    • AI
    • API
    • Approval
    • MCP
    • Custom Code
      • Libraries
        • MESA SDK
        • Filter
        • Loop
        • Transform
        • oAuth
        • Shopify
        • ShopifyGraphql
      • FAQ
    • Data
    • Delay
    • Email
    • Filter
    • Form
      • Configure
      • Going Further
      • Technical Notes
    • FTP
    • Image
    • Loop
    • Package Tracking
    • Paths
    • Schedule
    • Scraper
    • SMS
    • Transform
    • Virtual Output
    • Weather
    • Web Request
    • Webhook
  • Apps
    • Airtable
    • Amazon S3
    • Asana
    • Blog Studio
    • ChannelApe
    • Claude
    • ChatGPT
    • Dall-E 2
    • Delighted
    • Digital Humani
    • Discord
    • DocuSign
    • Dropbox
    • Etsy
    • Facebook
    • Fera.ai
    • Gatsby
    • Gmail
      • Send Email
    • Google Analytics 4
    • Google Analytics UA
    • Google Calendar
    • Google Drive
    • Google Forms
    • Google Sheets
      • Add Row
      • Query Rows
      • Update Row
      • Row Created
      • Row Updated (Advanced)
      • Creating New Spreadsheets
      • Technical Notes
    • Gorgias
    • Govalo
    • Help Scout
    • Hubspot
    • Infinite Options
    • Intercom
    • IPDetective
    • Judge.me
    • Katana
    • Klaviyo
      • API Deprecation
    • Loop Returns
    • Loyalty Lion
    • Mailchimp
    • Mailgun
    • Mandrill
    • Mantle
    • Notion
    • Odoo
    • Omnisend
    • Page Studio
    • Pinterest
    • Printful
    • PrintNode
    • QuickBooks
    • Rebuy
    • Recharge
    • Remove.bg
    • Returnly
    • Rivo
    • Salesforce
    • Segment
    • Sendlane
    • Shippo
    • ShipStation
    • Shopify
      • Technical Notes
        • Configuring Your Payload
        • Modifying and Filtering Get Lists
        • Parameters
        • Error Codes
        • Accuracy of orders_count Variable
        • Accuracy of Count Products Action
        • Using the Gift Cards API
        • How to Find a Specific Record in the Testing Interface
        • Order, Customer, and Product Updated Trigger Frequency
    • Shopify Flow
    • Shopify Plus
    • Shopify Retail POS
    • Skio Subscriptions
    • Slack
    • Smartrr
    • Smile.io
    • Square
      • Updating Inventory
      • Frequently Asked Questions
    • Stamped.io
    • Stripe
    • Thanks.io
    • TikTok
    • Tracktor
    • Twilio
    • Uploadery
    • Wonderment
    • Xero
    • Yotpo
    • Yotpo Loyalty
  • For developers
    • Admin API
    • Command Line Interface
    • Embedding templates
  • Frequently asked questions
    • Why isn't the log search returning logs with the search I entered?
    • Is it possible to handle errors or retry steps?
    • How do I handle a failed task?
    • Does MESA auto-save workflows?
    • Can I Use Apps That Don't Have a MESA Connector?
    • Why is my workflow action adding the same data each time it occurs?
    • How do I cancel automations that are already in progress?
    • How do I cancel my MESA subscription or 7-day trial?
    • Can you import code from npm in custom code?
    • Do you have a Slack Community?
Powered by GitBook
On this page
  • Where to Start
  • Did the error come from a connected app or MESA?
  • Common types of error messages
  • Look at app documentation for integration-specific errors
  • Inspecting Tasks
  • Turn on Debug Logs for Additional Visibility
  • Best Practices

Was this helpful?

  1. Workflow Activity
  2. Tasks

Troubleshooting

Learn the steps to patch up your workflow when it needs a quick fix! 🛠️

PreviousTasksNextReplay

Last updated 7 months ago

Was this helpful?

When your workflow isn't running as intended, you have the ability to troubleshoot and get things back on track.

Where to Start

The first step to understanding what's gone wrong is to check out the within your workflow.

Using the Status filtering in the right-hand sidebar, filter by "Error."

Once you can see the activity runs with errors, click one to expand the details of how the automation ran for each step. When you locate the step with the error, the next goal is to understand the error.

Below are some important things to consider when viewing the error message associated with your run.

Did the error come from a connected app or MESA?

  • Errors related to MESA built-in tools are specific to MESA requirements.

Common types of error messages

  • Access denied

  • Not found (404 error)

    • This typically occurs when a step requires an ID (e.g., Product ID, Order ID, Customer ID, etc.), but the value passed for the required ID field is invalid.

  • Bad request

    • This message can mean that the data being used was not accepted by the service you're using.

  • Timeout

    • An error message that mentions "timeout" typically means the service you're using has received too many requests within a short period of time or simply didn't process the request properly.

      • To troubleshoot these errors, you have a few recommended options:

        • Contact support

  • 503 and 502 errors

    • These errors are likely related to a temporary disruption with the service you're trying to connect to.

Look at app documentation for integration-specific errors

Inspecting Tasks

Inspecting a task allows you to dive into further technical details about the step and how it ran. With this additional insight, you can help make connections to what the error message is referring to regarding your errored run.

One way to inspect a task is to view the Request details. To do this, click on the three vertical dots icon on the right-hand side of the step in the Activity to reveal the Task Options.

With the request details open, you can identify what the step attempted to send (labeled Sent Body on the left) and what was returned (labeled Returned Body on the right).

The Returned Body message contains information that acknowledges the problem that created the error. Confirm whether or not this messaging makes sense compared to the information available in the Sent Body details.

Another way to breakdown activity data and determine what went wrong is to check the Variables available from steps in the workflow prior to the step that errored. This is especially helpful if you know the error is related to a variable that didn't pass its value properly (e.g. an Order ID or Product ID variable).

To check the variables available view, click on the three vertical dots icon featured on the right-hand side of a step in the Activity to reveal the Task Options.

With the variables available view open, click open each step's key to reveal the variables associated with each step. From here, you can confirm whether or not all of the variables you used in your workflow setup passed the values you were expecting.

Turn on Debug Logs for Additional Visibility

If you cannot resolve the error, you can perform additional troubleshooting by turning on Logging debug mode in the workflow's Activity tab.

1. In the Activity tab, turn on Debug logs while troubleshooting errors. Once you are done troubleshooting, you can turn off Debug logs mode.

2. Scroll or search within the Activity tab and locate the failed task with an Error status on the right-hand side.

3. Click on the ˇ icon to the left of the date. Every task in the workflow will then display.

4. Locate the error which displays with a red background color.

Since Logging and Logging debug mode are turned on, you will see more information related to the failed task appear.

The messages with the red Error tag will be the most important to review.

7. Once you have made adjustments to your workflow to fix the error, you can replay the failed task.

Debug logging details will show for any new activity runs that occur after enabling debug logging, so replaying a task or running a test allows you to recover these additional details from a previous run.

Best Practices

often have their own error messaging related to API requirements associated with the service. If you have a knowledge of APIs, you can often refer to API documentation for the specific app, if it's publicly accessible, to help break down the error message.

Credential issues often provide this message, meaning you may need to check, update, or re-add your to the step.

To troubleshoot, sent via the requested details or variables available.

To troubleshoot, that was sent and double-check your setup.

the activity run (and for error handling)

Upgrade

To troubleshoot, the activity run (and for error handling)

5. Replay the tasks starting from the while Logging debug mode is turned on. You can click on the three vertical dots icon on the first task. Click Replay to replay the task.

6. MESA provides a more detailed layout under the page. Logs enable you to search for past tasks or to view an entire chain of actions and its information for a specific task. You click on the three-dotted button on the first task and click on Logs.

You can also see your outputs by using an step in your workflow for testing purposes.

for your workflows.

Set up for errored task runs.

Connected apps
credential
look at the data
look at the data
credential
Replay
set up automatic replay
your plan
replay
setup automatic replay
Shopify technical error codes and explanations
Trigger
Logs
Activity Log
Enable failure notifications
automatic replay
Activity tab