Transmission Logs

Advanced

The Logs page tracks all communications between your Bigcommerce store and Profill services, providing transparency and helping you troubleshoot any issues.

What Are Logs?

Logs record every communication between your app and Profill services, including:

Product configuration submissions to Profill
Order submissions to Profill
Pricing and inventory synchronization
Fulfillment status updates
Product catalog requests from HIT

Log Information Display

Each log entry shows the following information in the table:

Table Columns:

Log ID — Unique identifier for each log
Service — Which service was contacted (HIT, Profill, etc.)
Request Type — The specific action performed
Resource ID — Related product or order ID
Status — Success or Failed
Created At — Date and time of the request
Actions — Delete button for individual log removal

Click a log to view details:

Request Endpoint — Full URL of the service contacted
Request Data — Complete information sent (formatted JSON)
Response Data — Complete response received (formatted JSON)
Copy Buttons — Easily copy request or response for support

Search & Filter Features

Easily find specific logs using these tools:

Search Box: Search by service name, request type, resource ID, or request URL
Status Filter: Filter by All, Success, or Failed
Pagination: View 20 logs per page with Previous/Next navigation
Clear Filters: Reset all filters and search at once

Viewing Log Details

Click any log row to open a detailed modal showing:

Header Information: Resource type, service name (with badge), resource ID, endpoint URL, status, and timestamp
Request Section: Complete JSON data sent to Profill with syntax highlighting
- Properly formatted and color-coded JSON
- Copy button to easily share with support team
- Shows "Copied!" confirmation when clicked
Response Section: Complete JSON response received from Profill
- Syntax-highlighted for readability
- Includes error messages, success confirmations, and returned data
- Copy button for easy sharing

Managing Logs

Delete Individual Logs

Each log row has a delete button (trash icon) in the Actions column.

Click the delete icon to remove a single log
Confirmation is immediate (no undo)
Useful for removing test logs or clearing specific entries

Bulk Delete by Date Range

When you have logs, a "Delete Logs" button appears:

Click "Delete Logs" in page header
Use calendar picker to select date range
Review the selected range (start to end dates)
Click "Delete Logs" to permanently remove

⚠ Warning: Deleted logs cannot be recovered. Bulk deletion only affects logs from your current environment (Development or Production), not both.

Environment Isolation

Logs are environment-specific:

Development logs are separate from Production logs
Switching environments shows logs for that environment only
Prevents confusion between test and live data
Allows safe testing without affecting production logs

Common Use Cases

Troubleshooting Failed Orders

Search for the order ID in logs to see what was sent and received. Check for error messages in the response to identify the issue.

Debugging Product Configuration Issues

Filter by "Failed" status to see which product submissions failed. Review request data to verify all required fields were sent correctly.

Monitoring Activity

Track how often the app communicates with Profill services. Identify patterns in successful vs. failed actions over time.

Verifying Data Sent to Profill

Confirm exact data sent to Profill for any operation. Useful for support tickets or when working with Profill technical team.

Empty State

When no logs are available, you'll see an informative empty state that explains:

What logs are and why they're useful
When logs will start appearing (after API requests are made)
Link to documentation for more information

Support Tip: Logs are invaluable for troubleshooting integration issues. When contacting support, copy the request/response JSON from the log detail modal to provide exact technical details. The syntax-highlighted viewer makes it easy to identify missing fields, incorrect data, or error messages.