Troubleshooting

Symptoms: Your webhook-triggered automation isn't running when external events occur.

Solutions:

1. Verify the webhook URL

   • Go to your automation's trigger settings
   • Copy the exact webhook URL
   • Ensure the external service is using the correct URL

2. Check the HTTP method

   • work.studio webhooks accept POST requests
   • Ensure the external service sends POST, not GET

3. Verify payload format

   • Webhooks expect JSON with Content-Type: application/json
   • Use the test panel to see what data is arriving

4. Check automation status

   • Ensure the automation is Active, not Draft
   • Toggle off and on to refresh

Symptoms: Your scheduled automation misses its scheduled time.

Solutions:

1. Verify timezone

   • Check that the schedule uses your intended timezone
   • Go to Settings → Workspace to confirm workspace timezone

2. Check schedule syntax

   • For cron expressions, validate at crontab.guru
   • Common mistake: * 9 * * * runs every minute at 9, not once at 9

3. Ensure automation is active

   • Draft automations don't run on schedule

4. Check run history

   • The run may have executed but failed
   • Review the Runs tab for errors

Symptoms: Clicking "Run" does nothing.

Solutions:

1. Save the automation first

   • Unsaved changes prevent test runs
   • Click Save, then Run

2. Check for validation errors

   • Look for red error indicators on actions
   • Fix required field errors

3. Browser issues

   • Clear browser cache
   • Try a different browser
   • Disable browser extensions

Error: Connection timeout or Connection refused

Solutions:

1. Check the connector configuration

   • Ensure the base URL is correct
   • Verify the operation exists in the connector
   • Test the connection directly

2. Check authentication

   • Verify the connection credentials are valid
   • Check that OAuth tokens haven't expired
   • Regenerate API keys if needed

3. Check network restrictions

   • Some APIs block requests from cloud IPs
   • Contact the API provider about allowlisting

4. Increase timeout

   • Default is 30 seconds
   • Increase for slow APIs in step settings

Error: 401 Unauthorized or 403 Forbidden

Solutions:

1. Verify credentials

   • Check that API key is correct in the connection
   • Regenerate the key if needed

2. Check scopes/permissions

   • Ensure the connection has required permissions
   • Some APIs require specific OAuth scopes

3. Re-authenticate OAuth connections

   • Go to Connections
   • Click Reconnect on the affected connection

Error: Connection refused or timeout

Solutions:

1. Verify connection details

   • Check host, port, database name
   • Ensure the database is accessible

2. Check credentials

   • Verify username and password
   • Ensure the user has required permissions

3. Check SQL syntax

   • Review the query for syntax errors
   • Test the query directly in a database client

Error: Permission denied

Solutions:

1. Check user permissions
   • Ensure the database user can access the schema
   • Grant necessary SELECT/INSERT/UPDATE permissions

Error: Execution error or Syntax error

Solutions:

1. Check JavaScript syntax

   • Look for missing brackets, semicolons
   • Validate code in a JS linter

2. Check data references

   • Ensure context.step references exist
   • Use optional chaining for uncertain data

3. Check return statement

   • FUNCTION must return a value
   • Missing return causes undefined output

Error: Cannot read property of undefined

Solutions:

1. Check data path

   • The referenced field may not exist
   • Use optional chaining: {{ input?.customer?.name }}

2. Verify data structure

   • Check the actual payload in run logs
   • The structure may differ from expected

3. Handle null values

   • Add defaults: {{ input.name || "Unknown" }}

Symptoms: A working connection suddenly shows disconnected.

Solutions:

1. Re-authenticate

   • Click the connection
   • Click Reconnect
   • Complete the OAuth flow again

2. Check app permissions

   • Go to the connected app (Slack, Salesforce, etc.)
   • Verify work.studio still has access
   • Revoke and re-grant if needed

3. Token expired

   • Enterprise apps may have short token lifetimes
   • Re-authenticate more frequently

Symptoms: Actions fail with authentication errors.

Solutions:

1. Regenerate the API key

   • In the external service, create a new API key
   • Update the Secret in work.studio

2. Check key permissions

   • Ensure the key has required scopes
   • Some APIs require admin keys for certain operations

3. Verify key format

   • Some keys need prefixes: Bearer, Token, ApiKey
   • Check the API documentation

Symptoms: Automation runs for minutes instead of seconds.

Solutions:

1. Identify the slow step

   • Check run logs for step durations
   • Look for the step taking longest

2. Optimize CONNECTOR calls

   • Batch requests when possible
   • Use pagination efficiently
   • Cache frequently-accessed data

3. Use parallel execution

   • Run independent steps in parallel
   • Reduces total execution time

4. Optimize DATABASE queries

   • Add indexes for frequently queried columns
   • Limit result sets with WHERE clauses
   • Avoid SELECT * when only some fields needed

Symptoms: Automation fails with timeout after 60 seconds.

Solutions:

1. Increase timeout

   • Go to automation settings
   • Increase max execution time (up to 15 minutes)

2. Break into smaller steps

   • Split long-running work
   • Use sub-workflows for complex operations

3. Optimize external calls

   • Slow third-party APIs may need caching
   • Consider webhooks instead of polling

Cause: Trying to access a property on undefined data.

Fix:

// Instead of:
{{ input.customer.name }}

// Use optional chaining:
{{ input?.customer?.name }}

// Or provide default:
{{ input.customer.name || "No name" }}

Cause: Referencing a step that doesn't exist or hasn't run yet.

Fix:

// Ensure step name is correct:
{{ steps.lookupCustomer.output.name }}

// Check step naming in your workflow
// Step names are case-sensitive

Cause: Using a function that doesn't exist in expressions.

Use FUNCTION step instead: For complex operations, use a FUNCTION step with JavaScript:

// In FUNCTION step:
const date = new Date(context.config.timestamp);
return {
  formatted: date.toISOString().split('T')[0]
};

Cause: Expression contains invalid syntax.

Common fixes:

• Balance brackets: {{ }} not { } or {{{ }}}
• Check operators: == not = for comparison
• Ensure variable names match step names exactly

Solutions:

1. Clear cache

   • Press Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac)
   • Or clear browser cache in settings

2. Try incognito mode

   • Rules out extension conflicts

3. Check browser compatibility

   • Use Chrome, Firefox, Edge, or Safari
   • Update to latest version

4. Check network

   • Ensure stable internet connection
   • Check if flow.work.studio is accessible

Solutions:

1. Check for validation errors

   • Red outlines indicate invalid fields
   • Fix errors before saving

2. Check connection

   • Network issues may prevent saves
   • Look for offline indicator

3. Session expired

   • Refresh the page
   • Log in again if prompted