Troubleshooting Polling Trigger Error Notifications

Overview

If you're receiving workflow error notifications every 12 hours, this indicates that a polling trigger in one of your published workflows is encountering issues and failing to execute properly.

Why Am I Getting These Notifications?

These recurring error notifications occur when:

  • A published workflow contains a polling trigger that is experiencing failures
  • The trigger encounters an unexpected issue during its scheduled execution
  • The workflow continues to attempt execution every 12 hours, generating notifications each time it fails

Step-by-Step Troubleshooting

Step 1: Locate the Problematic Workflow

  1. Check the error notification email you received
  2. Navigate to the specific workflow mentioned in the error message
  3. Open the workflow to review its current status and configuration

Step 2: Determine if the Workflow is Active

For Unused Workflows:

  • If this workflow is not currently being used in production but remains published, it will continue sending error notifications
  • Solution: Simply unpublish the workflow to stop the alerts
  • The notifications should cease once the workflow is unpublished

For Active/Live Workflows:

  • If this is a workflow currently in use, proceed to Step 3

Step 3: Verify Authentication Settings

For live workflows experiencing errors:

  1. Check all platform authentications used within the workflow
  2. Ensure all connected services have valid, current authentication credentials
  3. Look for any expired tokens or disconnected integrations

Step 4: Manual Troubleshooting

If authentication appears correct, try these additional troubleshooting steps:

  1. Test the trigger manually
    • Navigate to the workflow trigger settings
    • Use the manual test feature to check if the trigger executes successfully
    • Review any error messages that appear during manual testing
  2. Reconnect OAuth2 Authentication (if applicable)
    • If your trigger uses OAuth2 authentication, try disconnecting and reconnecting the authentication
    • This can resolve issues with expired or corrupted authentication tokens
    • Follow the reconnection process for your specific platform integration

When to Contact Support

If you have completed all the above steps and are still experiencing issues:

  • All authentications are verified as correct
  • Manual trigger testing continues to fail
  • The workflow is essential for your operations

Please contact our support team at support@keragon.com with the following information:

  • The specific workflow name and ID
  • When did the errors start
  • Steps you've already taken to troubleshoot
  • Screenshots of any error messages or authentication screens

Our team will investigate the issue further and provide additional assistance.

Prevention Tips

To avoid future workflow error notifications:

  • Regularly review and maintain your published workflows
  • Unpublish workflows that are no longer needed
  • Monitor authentication expiration dates for connected platforms
  • Test workflows periodically to ensure continued functionality
  • Keep integrations and connected services up to date

Related Articles

Was this article helpful?
0 out of 0 found this helpful

Articles in this section