Activity Logging

Monitor, debug, and troubleshoot your workflows with activity logs.

Overview

Activity logging provides visibility into your workflow executions. Every time a workflow runs, Sequensy logs detailed information about what happened, making it easy to monitor, debug, and optimize your automations.

Accessing Activity Logs

  1. Go to Sequensy in your WordPress admin
  2. Click Activity in the top menu
  3. Browse and filter log entries

Log Entry Structure

Each log entry contains:

FieldDescription
TimestampWhen the execution occurred
WorkflowWhich workflow ran
TriggerThe event that started it
StatusSuccess, failed, or partial
DurationHow long execution took
ActionsList of actions executed

Log Levels

Sequensy uses four log levels:

Debug

Detailed technical information for troubleshooting:

  • Variable values
  • API requests/responses
  • Step-by-step execution flow

Info

Normal operational events:

  • Workflow started
  • Action completed
  • Workflow finished

Warning

Non-critical issues that didn’t stop execution:

  • Empty optional field
  • Retry attempted
  • Fallback used

Error

Problems that caused failure:

  • Action failed
  • Invalid data
  • API error
  • Connection timeout

Filtering Logs

By Workflow

View logs for a specific workflow:

  1. Click the workflow filter
  2. Select the workflow
  3. View only its executions

By Level

Filter by severity:

  • Show only errors for troubleshooting
  • Show all for complete picture

By Date Range

View logs from specific time periods:

  • Today
  • Last 7 days
  • Last 30 days
  • Custom range

By Status

Filter by execution result:

  • Success - Completed without errors
  • Failed - One or more errors
  • Partial - Some actions succeeded

Reading Log Details

Click any log entry to see details:

Execution Summary

Workflow: Welcome New Users
Trigger: User Registered
Started: 2024-01-15 10:30:45
Duration: 1.2s
Status: Success

Action Details

[1] Send Email
    To: john@example.com
    Subject: Welcome, John!
    Status: Sent
    Duration: 0.8s

[2] Add to Mailchimp
    Email: john@example.com
    List: Newsletter
    Status: Subscribed
    Duration: 0.4s

Variable Values

Trigger Data:
  user_id: 42
  user_email: john@example.com
  first_name: John
  last_name: Doe
  role: subscriber

Troubleshooting with Logs

Workflow Not Running

Check if trigger fired:

  1. Filter by workflow
  2. Look for any recent entries
  3. If none, trigger conditions may not be met

Action Failing

Find the error:

  1. Open the log entry
  2. Find the failed action
  3. Check error message
  4. Review input data

Wrong Data

Verify variable values:

  1. Open log entry details
  2. Check “Trigger Data” section
  3. Compare expected vs actual

Common Error Messages

ErrorCauseSolution
Invalid emailBad email formatCheck variable
Connection timeoutAPI unreachableRetry later
Authentication failedBad credentialsReconnect integration
Not foundRecord doesn’t existCheck ID/reference
Rate limitedToo many requestsSpace out workflows

Log Retention

Activity logs are retained based on your settings:

SettingRetention
Default30 days
Debug Mode7 days (more detail)
Extended90 days (Pro)

Old logs are automatically deleted to manage database size.

Performance Insights

Use logs to understand workflow performance:

Execution Time

  • Average duration per workflow
  • Slow actions identification
  • Peak execution times

Success Rates

  • Overall success percentage
  • Problematic workflows
  • Common failure points

Volume Tracking

  • Executions per day/week
  • Trigger frequency
  • Action volume

Best Practices

Regular Monitoring

  • Check logs daily for errors
  • Review failed executions promptly
  • Monitor new workflows closely

Debugging Workflow

  1. Reproduce the issue
  2. Find the log entry
  3. Check trigger data
  4. Walk through each action
  5. Identify where it failed
  6. Fix and test again

Optimizing Performance

  1. Review slow executions
  2. Identify bottleneck actions
  3. Consider alternatives
  4. Monitor improvement

Managing Log Size

  • Use appropriate retention
  • Clear old debug logs
  • Export important logs if needed

Exporting Logs

Export logs for analysis or compliance:

  1. Filter to desired entries
  2. Click Export
  3. Choose format (CSV, JSON)
  4. Download file