Skip to content
English
Claudio
  • There are no suggestions because the search field is empty.

How do I see logs for my submitted jobs?

This article summarizes how to monitor webhook logs in Loom Analytics.

Description: The Webhook Logs page provides a comprehensive view of all webhook events triggered by your account. This interface allows you to monitor webhook delivery success rates, response times, and troubleshoot any failed webhook attempts. All webhook activity is permanently stored and accessible for review.

Accessing Webhook Logs

  1. Log in to your Loom Analytics account
  2. Click on the gear icon on top-right corner.
  3. Navigate to Integrations.
  4. Click on Webhook Logs

 

Dashboard Overview

At the top of the Webhook Logs page, you'll see key metrics:

  • Total: Total number of webhook events recorded
  • Success: Number of successful webhook deliveries (HTTP 200)
  • Failed: Number of failed webhook attempts (HTTP 503 or other errors)
  • Rate: Success rate percentage (e.g., 97.73%)
  • Avg Time: Average response time from your webhook endpoint (e.g., 73ms)

These metrics provide an at-a-glance view of your webhook health and performance.

Filtering Webhook Logs:

Status Filter

Filter logs by delivery status:

  • All: Shows all webhook events regardless of status
  • Success: Shows only successful deliveries (HTTP 200)
  • Failed: Shows only failed webhook attempts (HTTP 503)

 

Date Range Filter

View webhook logs from different time periods:

  • Last 24 hours: View webhooks from the past day
  • Last 7 days: View webhooks from the past week (default)
  • Last 30 days: View webhooks from the past month
  • Last 90 days: View webhooks from the past quarter

 

Search by Job ID

Use the search field to find webhooks for a specific job:

  1. Enter the Job ID in the "Search Job ID" field
  2. The results will filter to show only webhook events for that job

 

Understanding Log Entries

Each webhook log entry displays the following information:

Column Description
Job ID The unique identifier for the job that triggered the webhook.
Event Type The type of event that occurred (e.g., job.completed, job.failed)
Status HTTP status code returned by your webhook endpoint
Response Time How long your endpoint took to respond (e.g., 93ms, 109ms)
Timestamp Date and time when the webhook was sent

 

Status Codes

Status Code Badge Color Meaning
200 Green Success - Your webhook endpoint received and acknowledged the request
503 Red Failed - Your webhook endpoint was unavailable or returned an error

 

Viewing Webhook Details

To view detailed information about a specific webhook event:

  1. Click the dropdown arrow (▼) next to any Job ID
  2. The expanded view shows:
    • Webhook URL: Your configured webhook endpoint URL
    • Response Body: The complete JSON payload that was sent to your endpoint
Sample Response Body
{
    "event": "job.completed",
    "status": "completed",
    "job_name": "Postman_OpenAPI_0122",
    "timestamp": 1769194750,
    "completed_at": "2026-01-23 18:59:06",
    "error_message": null,
    "job_reference_id": "S3Ol3oform6973c4b108f18"
}


Refreshing Webhook Logs

The Webhook Logs page does not auto-refresh. To see the latest webhook events:

  1. Click the refresh icon in the top-right corner
  2. The page will reload with updated webhook data

Note: If you have submitted multiple jobs (e.g., 100 jobs), you may need to refresh several times as jobs are processed in batches. Webhooks are triggered as each job completes, so new log entries will appear gradually.

Pagination

Webhook logs are displayed in pages for better performance:

  • 50 entries per page: Each page shows up to 50 webhook log entries
  • Use pagination controls at the bottom to navigate between pages
  • Filters and search apply across all pages

 

Data Retention

Webhook logs are stored permanently with no retention limit. All webhook events remain accessible indefinitely for compliance, auditing, and troubleshooting purposes.

 

Troubleshooting with Webhook Logs

Identifying Failed Webhooks

  1. Use the Status filter and select "Failed"
  2. Review failed entries to identify patterns (e.g., specific time periods, types of jobs)
  3. Expand failed entries to see the webhook URL and payload
  4. Check if your server was down or experiencing issues at the timestamp shown

Monitoring Response Times

  • High response times (>1000ms) may indicate performance issues with your webhook endpoint
  • The Avg Time metric helps you track overall endpoint performance
  • Individual log entries show per-webhook response times

Verifying Webhook Delivery

  1. Use the Search Job ID field to find webhooks for a specific job
  2. Verify that a webhook was sent when expected
  3. Check the status code to confirm successful delivery
  4. Expand the entry to review the exact payload sent


Common Issues

Webhook shows Status 503 (Failed)

Possible Causes:

  • Your webhook endpoint was unreachable at the time
  • Your server returned an error (5xx status code)
  • Network connectivity issues between Loom Analytics and your server
  • Your endpoint took too long to respond (timeout)

Solution:

  • Check your server logs at the timestamp shown in the webhook log
  • Verify your webhook URL is correct in the Webhooks configuration
  • Ensure your endpoint returns HTTP 200 within a reasonable timeframe
  • Test your webhook using the "Test Webhook" button in Webhooks settings


Issue: No webhook logs appearing for submitted jobs

Possible Causes:

  • Webhook is not configured or not active
  • Jobs were submitted before webhook was configured
  • You're looking at the wrong date range

Solution:

  • Go to Integrations > Webhooks and verify your webhook status is "Active"
  • Webhooks only trigger for jobs submitted after webhook configuration
  • Adjust the Date Range filter to expand your search period
  • Click the refresh icon to ensure you're viewing the latest data

 

Learn more about how Loom Analytics signs and secures webhook requests here.