Troubleshooting Workflows

Troubleshoot common workflow issues including trigger failures, execution errors, and browser problems

When workflows don't behave as expected, it can be frustrating to diagnose the issue. This guide covers the most common workflow problems and their solutions using Noloco's built-in debugging tools.

Common Workflow Issues

Workflows Not Triggering

External Data Source Changes Don't Trigger Workflows

Problem: You create or update a record directly in Airtable, Google Sheets, or another external data source, but your Noloco workflow doesn't run.

Why this happens: Workflows only trigger when changes are made through your Noloco app interface or API, not when changes are made directly in external data sources.

Solutions:

• Make changes through your Noloco app instead of directly in the external data source

• Use the external data source's native automation features (e.g., Airtable Automations, Zapier) to trigger webhooks to Noloco

• Set up a scheduled sync and use time-based triggers instead of record-based triggers

This is by design to prevent infinite loops and ensure reliable workflow execution. External data sources sync to Noloco, but don't trigger workflows during the sync process.

Workflow Triggers Intermittently

Problem: Your workflow sometimes runs and sometimes doesn't, even when triggered the same way.

Debugging with workflow history:

1. Go to your workflows page

2. Find your workflow and click "Run history"

3. Compare successful runs vs failed/missing runs

4. Look for patterns in the trigger data

Common causes:

• Field validation: Check if required fields are properly filled when the trigger fires

• Permissions: Ensure the user triggering the workflow has appropriate permissions

• Workflow conditions: Review any "Only continue if" conditions that might be preventing execution

Browser and Interface Issues

Chrome "Aw Snap" Errors on Workflows Screen

Problem: You get "Aw snap! Something went wrong" errors when trying to access or edit workflows in Chrome.

Solutions:

1. Try a different browser: Test in Safari, Firefox, or Edge to isolate if it's Chrome-specific

2. Check workflow complexity: Very large workflows with many actions can cause browser memory issues

3. Edit in smaller sections: If you have a complex workflow, try editing individual actions rather than the entire workflow at once

If the problem persists across browsers, it may be a platform issue. Contact support with details about your workflow complexity and any browser console errors.

Step-by-Step Debugging Process

1. Use Workflow History as Your Primary Tool

Access workflow history:

1. Navigate to https://portals.noloco.io/~/_/workflows

2. Find your workflow and click "View runs"

3. Examine recent runs for errors, failed actions, or unexpected data

What to look for:

• Error messages in failed runs

• Missing runs when you expected the workflow to trigger

• Successful runs with unexpected output data

• Timing patterns in workflow execution

2. Test Workflows Manually

For on-demand workflows:

• Use action buttons to trigger workflows with known test data

• Compare results with your expectations

For automatic workflows:

• Create test records that should trigger the workflow

• Use simple, known-good data for testing

• Monitor workflow history immediately after creating the test trigger

3. Isolate Problem Areas

Identify the failure point:

• Look at workflow history to see which step fails

• Check if the workflow starts but doesn't complete

• Verify if all expected actions executed

Test individual components:

• Temporarily disable actions to isolate issues

• Test with minimal data to reduce variables

• Re-enable actions one by one to pinpoint problems

4. Review Workflow Logic

Check trigger conditions:

• Verify the trigger type matches your use case

• Review any field-specific triggers (watched fields)

• Ensure trigger permissions are correct

Validate action setup:

• Confirm all required fields are mapped correctly

• Check that dynamic data references are valid

• Verify external service configurations (webhooks, emails)

Specific Error Scenarios

Workflows Start But Don't Complete

Use workflow history to diagnose:

1. Find the incomplete workflow run

2. Identify the last successful action

3. Check the error message for the failed action

4. Review the data available at the point of failure

Common solutions based on workflow history:

• Missing data: Ensure all required fields are populated before the action

• Permission errors: Verify the workflow has access to referenced records

• External service issues: Check webhook endpoints or email configurations

Step 3 Automation Workflow Errors

Problem: You encounter "unexpected behavior" in step 3 of your automation workflow.

Debugging approach:

1. Review workflow history for the specific run that failed

2. Check step 2 output: Ensure step 2 completed successfully and provided expected data

3. Verify step 3 configuration: Confirm all field mappings and conditions are correct

4. Test with simplified data: Create a test scenario with minimal data to isolate the issue

Email Actions Not Sending

Troubleshooting with workflow history:

1. Check if the email action shows as "completed" in workflow history

2. Look for error messages related to email delivery

3. Verify the email addresses in the workflow run data

4. Review SMTP configuration if using custom email settings

Webhook Actions Timing Out

Using workflow history to diagnose:

1. Look for timeout error messages in the workflow run

2. Check the webhook URL and payload data in the run details

3. Verify the external service is responding by testing the webhook URL separately

Getting Help

When contacting support about workflow issues, provide:

1. Workflow run ID from the workflow history

2. Timestamp of the failed or missing run

3. Screenshots of the workflow history showing the issue

4. Expected vs actual behavior description

The workflow history contains most of the information needed to diagnose issues. Always check there first before reporting problems.

Visit Noloco Community to see if others have experienced similar workflow issues.