TCC – Troubleshooting Report Reference

Version 1.1.1 | January 2026

This document explains each field in the Trados Callback Catcher troubleshooting window, its diagnostic value, and security considerations when sharing publicly.

Overview

The troubleshooting window displays comprehensive diagnostic data captured when TCC receives a webhook. This information helps developers debug delivery issues, verify configuration, and generate support tickets.

The Copy All button generates a formatted report containing all displayed fields, suitable for support tickets.

Security Considerations Summary

Risk Level Meaning
🟢 Safe No concerns sharing publicly
🟡 Session-bound Safe after tunnel session ends
🟠 Consider redacting Contains identifiers you may prefer not to share publicly
🔴 Redact Contains account-specific identifiers

Most fields are safe to share. The main considerations are:

  • Tenant ID — identifies your Trados account (required for RWS support, redact for public posts)

  • Account ID (in payload) — identifies your Trados account

  • Application/Webhook IDs — identify your integration configuration

  • Project names — may contain client information (your choice)

Report Sections

Event Summary

Tenant Name

Example: My Production Tenant

The display name of the configured Trados tenant.

Troubleshooting value: Confirms which tenant configuration was active when the webhook was received. Essential when working with multiple tenants to ensure webhooks are matched to the correct configuration.

Security: 🟢 Safe — This is a display name you configured in TCC, visible only to you.

Tenant ID

Example: 68a4f1d09e6b3a725c0f2e91

The Trados Account ID (24-character hex string) of the configured tenant.

Troubleshooting value: Required for RWS support tickets. This identifies your specific Trados account and allows support engineers to investigate server-side issues.

Security: 🔴 Redact for public posts — Identifies your Trados account. Safe to share with RWS support (they need it), but consider redacting in fully public documentation or blog posts.

Event Type

Example: PROJECT.TASK.CREATED

The webhook event type.

Troubleshooting value: Identifies what happened in Trados Cloud. See API Reference for the full list.

Security: 🟢 Safe — Documented public API information.

Event ID

Example: 696d7a2c5f1e4863a9c0e4d7

Trados Cloud’s identifier for this event.

Troubleshooting value: Reference specific events in support tickets or debugging.

Security: 🟢 Safe — Event-specific, cannot access anything.

Timestamp

Example: 2026-01-17T12:23:17.361553251Z

When the event occurred in Trados Cloud (UTC).

Troubleshooting value: Establish event ordering. Webhook delivery order is not guaranteed, so use this for actual sequence.

Security: 🟢 Safe — Timestamp only.

Task Type

Example: Hold for Feedback (hold-for-feedback)

The workflow task type (for task events).

Troubleshooting value: Identifies which workflow step triggered the event.

Security: 🟢 Safe — Standard task types are public. Custom names are your choice to share.

Project Name

Example: 06 - TCC

The project name from the payload.

Troubleshooting value: Identifies which project generated the event.

Security: 🟠 Consider redacting — Project names often contain client names or job codes. Your choice whether to share.

Project ID

Example: 696b7f016c2a68053ac32887

The project identifier.

Troubleshooting value: Reference specific projects in API calls or support tickets.

Security: 🟢 Safe — Cannot access projects without credentials.

Network & Connection

Source IP (forwarded)

Example: 18.184.56.150

The IP address of the Trados Cloud server that sent the webhook, from the X-Forwarded-For header.

Troubleshooting value: Confirms requests originate from Trados Cloud infrastructure (AWS). Essential for firewall configuration and verifying you’re receiving genuine webhooks rather than spam or attacks.

Security: 🟢 Safe — This is Trados Cloud’s public infrastructure IP, visible to anyone receiving webhooks.

Direct Connection IP

Example: [::1]:59449

The IP address that directly connected to TCC’s HTTP listener, from Request.RemoteEndPoint.

Troubleshooting value: When using a tunnel (ngrok/Serveo), this shows localhost ([::1] or 127.0.0.1). If it shows an external IP, requests are bypassing the tunnel — indicating misconfiguration or direct attacks on your machine.

Security: 🟢 Safe — Shows localhost when tunnelling correctly, which reveals nothing.

Effective Source

Example: 18.184.56.150 (via [::1])

Combined view showing the original sender and connection path.

Troubleshooting value: Quick confirmation that the delivery chain is working: Trados Cloud → Tunnel → Local. Anomalies here indicate routing issues.

Security: 🟢 Safe — Combines the two fields above.

User-Agent

Example: ReactorNetty/X.X.XX

The HTTP client identifier from Trados Cloud.

Troubleshooting value: Confirms requests come from Trados Cloud’s HTTP client. Unexpected values indicate non-Trados traffic hitting your endpoint.

Security: 🟢 Safe — Identifies Trados Cloud’s software, not yours.

Timing & Delivery

Request Received

Example: 2026-01-17 13:23:11.428

Local timestamp when TCC received the webhook.

Troubleshooting value: Compare with Transmission Time to calculate network latency. Large gaps indicate network routing issues or tunnel delays.

Security: 🟢 Safe — Local timestamp only.

Response Sent

Example: 2026-01-17 13:23:11.428

Local timestamp when TCC sent the HTTP response.

Troubleshooting value: Combined with Request Received, shows TCC’s processing time.

Security: 🟢 Safe — Local timestamp only.

Response Time

Example: 0.7 ms or 2847.3 ms ⚠️

Milliseconds between receiving the request and sending the response.

Troubleshooting value: Critical metric. Trados Cloud requires responses within 3 seconds (single) or 20 seconds (batched). Values approaching these limits risk timeouts and retries. TCC shows ⚠️ when exceeding 2.5 seconds.

Common causes of slow response:

  • High CPU load on your machine

  • Antivirus scanning HTTP traffic

  • Tunnel provider latency

Security: 🟢 Safe — Performance metric of your local system.

HTTP Response Status

Example: 200 OK

The HTTP status code TCC returned to Trados Cloud.

Troubleshooting value: Confirms successful receipt. Non-2xx triggers Trados Cloud retries. If you see retries but TCC shows 200 OK, the problem is upstream (tunnel or network).

Security: 🟢 Safe — Standard HTTP status.

Request Integrity

Content-Type

Example: application/json

The MIME type from the request header.

Troubleshooting value: Should always be application/json for Trados webhooks. Other values indicate malformed requests or non-Trados traffic.

Security: 🟢 Safe — Standard header.

Content-Length (header)

Example: 470 bytes

The declared payload size from the HTTP header.

Troubleshooting value: Compare with Actual Body Size to detect truncation.

Security: 🟢 Safe — Size indicator only.

Actual Body Size

Example: 470 bytes

The actual bytes received by TCC.

Troubleshooting value: If smaller than Content-Length, the payload was truncated. This causes JSON parsing failures and signature verification failures. TCC shows ⚠️ on mismatch.

Common causes:

  • Network timeout during transfer

  • Proxy/firewall truncating payloads

  • Tunnel connection issues

Security: 🟢 Safe — Size indicator only.

HTTP Method

Example: POST

The HTTP method used.

Troubleshooting value: Trados webhooks always use POST. Other methods indicate non-webhook traffic or misconfigured clients hitting your endpoint.

Security: 🟢 Safe — Standard HTTP method.

Target Endpoint

Example: http://034635f58a16.ngrok.app:5000/callback

The URL that received the webhook.

Troubleshooting value: Confirms which tunnel URL was active. Helps debug why webhooks went to an old URL or verify correct configuration.

Security: 🟡 Session-bound — Tunnel URLs become invalid when you stop the tunnel.

Retry & Delivery Diagnostics

Retry Attempt

Example: 0 (first delivery) or 2 (retry after: timeout)

Whether this is the original delivery or a retry, with the failure reason if retrying.

Troubleshooting value: Non-zero indicates Trados Cloud had trouble delivering. The reason tells you what went wrong:

Reason Meaning Action
timeout Endpoint didn’t respond in time Check Response Time, reduce processing
connection_refused Endpoint unreachable Check tunnel is running
5xx Endpoint returned server error Check TCC logs

Trados Cloud retries up to 8 times over ~59 hours.

Security: 🟢 Safe — Delivery status only.

Correlation & Tracing

Trados Cloud Trace ID

Example: c3e5a9d1-7b2f-4a8c-b2e1-91f4d0a6c8e3_et_5f1a9c2e-3b7d-11f0-b4a2-acde9182f7c3

Distributed tracing identifier from X-Lc-Traceid.

Troubleshooting value: The key field for RWS support escalations. Include this when raising tickets — it allows RWS engineers to trace the request through their entire infrastructure.

Format: {Event UUID}_et_{Time-based UUID}

The parsed components are shown for reference but the full ID is what support needs.

Security: 🟢 Safe — Designed to be shared with support. Cannot access accounts; only meaningful to RWS engineers with backend access.

X-LC-Application

Example: 3c9e1f0a7b5d4826a4f8e2d9

Your Application ID from the header.

Troubleshooting value: Confirms which Application configuration sent the webhook. Useful if you have multiple Applications and need to verify the correct one is triggering.

Security: 🟠 Consider redacting — Identifies your specific integration. Cannot access your account without credentials, but reveals that this Application exists. Safe in support tickets; consider redacting in fully public posts.

X-LC-Webhook

Example: 4d9f3a2e6c1b8f507a4e0d9c

Your Webhook subscription ID from the header.

Troubleshooting value: Identifies which webhook configuration triggered the delivery. Useful when debugging subscription settings.

Security: 🟠 Consider redacting — Same as Application ID.

X-LC-Region

Example: eu

The Trados Cloud region from the header.

Troubleshooting value: Confirms which regional infrastructure handled the event. Important when you have accounts in multiple regions.

Security: 🟢 Safe — Public information (EU and CA are the options).

X-LC-Transmission-Time

Example: 2026-01-17T12:23:17.38473294

When Trados Cloud sent the webhook (ISO 8601).

Troubleshooting value: Compare with Request Received to calculate end-to-end latency. Also used in signature verification.

Security: 🟢 Safe — Timestamp only.

Signature Verification

Status

Example: ✓ Signature verified or ✗ Signature invalid or ○ Skipped

The verification result.

Troubleshooting value: Confirms webhook authenticity.

Status Meaning Action
✓ Verified Authentic, from Trados Cloud None needed
✗ Invalid Signature mismatch Check Secret Key config, check payload integrity
○ Skipped No Secret Key configured Configure if verification needed

Security: 🟢 Safe — Result only.

Algorithm

Example: SHA256withRSA

The signing algorithm from X-LC-Signature-Algo.

Troubleshooting value: Confirms expected algorithm. Unexpected values indicate non-standard requests.

Security: 🟢 Safe — Standard algorithm identifier.

CRC32

Example: 2535096151

Checksum of the request body, calculated by TCC.

Troubleshooting value: Intermediate value used in signature verification. Primarily useful for developers implementing their own verification who want to compare against TCC’s calculation.

Security: 🟢 Safe — Mathematical checksum, reveals nothing about content.

Verification String

Example: |2026-01-17|T12:23:17.38473294|696-aa2|3d4-f67|15e-178|6e0-ag8|696-aaa|443-b4d|cf6-23f|efe-796|

The string constructed for signature verification.

Troubleshooting value: Shows exactly what TCC signed for verification. Useful for developers implementing their own verification to compare string construction.

Security: 🟠 Consider redacting — Contains Application and Webhook IDs. Also reveals the signature construction format.

Signature

Example: gVDtgNEYXIz15zz4o2AkY+PoPbbF0v6k43qF...

The Base64-encoded RSA signature from X-LC-Signature.

Troubleshooting value: The actual signature for verification. Useful for developers debugging their own verification implementation.

Security: 🟢 Safe — Cannot be reused without the private key (which only Trados Cloud has).

Payload Fields (JSON Body)

These fields appear in the raw payload view, not the troubleshooting summary.

accountId

Example: 687c1a4d0b7f2368c2a8f9e1

Your Trados Account ID (tenant ID).

Troubleshooting value: Confirms which account the event originated from. Useful if you work with multiple accounts.

Security: 🔴 Redact — Identifies your Trados account. This is the same value you configure as Tenant ID. Always redact in public posts.

location.id

Example: 6544e7d1f05b6283e9a4d6f1c2b8e970

The folder/location ID within your account.

Troubleshooting value: Identifies where in your folder structure the event originated. Rarely needed for webhook troubleshooting.

Security: 🟠 Consider redacting — Reveals your account’s folder structure.

Headers (Full View)

The webhook detail view shows all headers. Some are captured for reference but have limited troubleshooting value:

Monitoring Headers (Traceparent, Tracestate, X-Dynatrace)

Internal distributed tracing and APM headers.

Troubleshooting value: Generally not useful for developers. RWS support may request these for deep infrastructure investigation.

Security: 🟢 Safe for you. These are Trados Cloud’s internal monitoring data.

Common Troubleshooting Scenarios

Webhooks not arriving

  1. Check Source IP — if blank, requests aren’t reaching TCC

  2. Verify tunnel is running and URL matches Target Endpoint

  3. Check firewall allows connections from AWS IP ranges

Signature verification failing

  1. Confirm Status shows ✗ Invalid (not ○ Skipped)

  2. Verify Secret Key is correctly configured in TCC

  3. Check Payload Integrity — truncated payloads fail verification

  4. Compare Verification String if implementing your own verification

Intermittent failures

  1. Check Retry Attempt — non-zero indicates previous failures

  2. Review Response Time — approaching 3 seconds risks timeouts

  3. Look for patterns in Transmission Time vs Request Received gaps

Support escalation

When contacting RWS support, include:

  1. Tenant ID — identifies your account

  2. Trace ID — essential for server-side investigation

  3. Response Time and HTTP Response Status — proves your endpoint responded

  4. Retry Attempt — shows delivery history

  5. Full troubleshooting report from Copy All

Sharing Guidelines

For RWS Support Tickets

Share the complete report. All fields are appropriate for private support.

For Blog Posts / Public Documentation

Consider redacting:

  • Tenant ID — identifies your account

  • accountId — always redact

  • X-LC-Application / X-LC-Webhook — optional, depends on context

  • Project Name — if it contains client information

  • Verification String — contains IDs

Everything else is safe to share.

Document generated for Trados Callback Catcher v1.1.1