fbpx
|
/ Documentation /Tips & Tricks/ SureTriggers Troubleshooting Guide: Resolve Common Issues Quickly and Easily

SureTriggers Troubleshooting Guide: Resolve Common Issues Quickly and Easily

While we’re always ready to help you with anything that you need help with by opening a ticket, before reaching out for support, try these quick troubleshooting steps to resolve common SureTriggers issues:

These steps can help with issues related to:

  • Using a WordPress-related connection: issues related to using automatically generated connections with locally installed plugins and multiple site connections
  • Functionality: any problem with how SureTriggers functions on your site
  • Non-triggered or duplicate workflow runs: bear in mind that some triggers are scheduled. More information about scheduled triggers can be found here: https://suretriggers.com/docs/triggers/
  • Errors related to fetching data and testing actions: these include undefined pluggable data, no data found to update, etc.

Troubleshooting Steps:

  1. Update SureTriggers: Ensure you’re using the latest version for optimal performance.
  2. Clear Cache: Clear your browser cache, cookies, and WordPress site cache to eliminate temporary data causing conflicts.
  3. Enable REST API for SureTriggers (if applicable): If you use a security plugin like Perfmatters, enable REST API to prevent issues with using connections.
  4. Check for plugin conflicts: Temporarily disable other plugins one by one to identify potential conflicts with SureTriggers. 
  5. Recreate workflows (if the issue is specific): If only a specific workflow has an issue, try recreating it from scratch instead of duplicating it to confirm the problem.
  6. Check connections: Make sure apps are connected properly under SureTriggers > Apps.
    1. For integrated SAAS-based platforms that require a paid plan, you may need to update the token if you were testing with one generated on a trial account.
    2. Check for any console errors, especially connection errors. 
    3. For  the common 500 server error, refresh the connection or have it deleted and generate a new API token to connect again.
  7. Check workflow history: Confirm if the workflow was triggered, if it is in progress due to a pending delay or scheduled step, or if it failed while being executed. In cases of failure, check under the “Data out” section for the failed step to see reasons why it failed, perhaps a wrong data format was passed from a trigger to the action fields.

Remember:

  • Try steps one at a time, checking if the issue persists after each step to isolate the problem.
  • Read the help text and refer to our documentation when setting up workflows

Additional Resource:

If you’ve tried these steps and still experience issues, please contact SureTriggers support for further assistance.

SureTriggers is committed to your success!

Before reaching out for support, we encourage you to check our documentation. Many common issues and solutions are readily available online, saving you time and effort. 

If you can’t find the answer you’re looking for, our support team is here to help. Don’t hesitate to reach out!

Was this doc helpful?
What went wrong?

We don't respond to the article feedback, we use it to improve our support content.

Need help? Contact Support
On this page
Scroll to Top