FastBound Integration - Error Log & Troubleshooting

The Error Log captures every sync failure, API error, and disposition issue that occurs during FastBound integration operations. Use it to diagnose problems, retry failed operations, and keep your integration running smoothly.

Accessing the Error Log

The Error Log is located on the FastBound Dashboard page, below the Sync Dashboard section:

Navigate to Business > Integrations > FastBound > Sync Dashboard.
Scroll down past the sync status cards and queue section.
The Error Log section appears with its own account selector and filters.

Filtering Errors

The Error Log provides several filters to help you find specific issues:

Account Filter

Select which FastBound account's errors to view. If you have multiple accounts, each has its own error history.

Error Type Filter

Filter errors by the operation that caused them:

Type	Description
Sync Acquisitions	Errors during acquisition sync from FastBound
Sync Contacts	Errors during contact sync from FastBound
Sync Items	Errors during item metadata sync
Create Disposition	Errors when creating dispositions in FastBound
API Error	General FastBound API communication errors

Show Dismissed Toggle

By default, dismissed errors are hidden. Toggle Show Dismissed on to view previously dismissed errors.

Understanding Error Entries

Each error entry in the table shows:

Column	Description
Actions	Buttons to retry, dismiss, or view details (see below)
Severity	Color-coded badge: red for Error, yellow for Warning, blue for Info
Type	The operation that triggered the error (e.g., Sync Acquisitions)
Message	A brief description of what went wrong (truncated to 80 characters in the list)
Entity	The specific record involved, if applicable (e.g., serial number, contact ID, order)
Date	When the error occurred

Error Actions

Each error row has action buttons depending on its state:

Retry (redo icon)

Available on retryable errors that haven't been dismissed. Requeues the failed operation for another attempt. Useful when errors were caused by temporary issues (network timeouts, rate limits).

Retry Queue Item (sync icon)

Available when the error is linked to a specific queue item. Retries the entire queue operation rather than just the individual error. A confirmation modal shows the error type and message before proceeding.

Dismiss (eye-slash icon)

Marks the error as acknowledged and hides it from the default view. Use this for errors you've investigated and resolved, or for errors that don't require action.

Details (info icon)

Opens a detail modal with the full error information:

Severity and Type
Full error message (not truncated)
Entity type and ID (if applicable)
Account name
Retry count and last retry timestamp
Date of the error
Full details - Raw error data displayed in a formatted JSON/text view

Bulk Actions

Dismiss All

Click the Dismiss All button in the top-right corner of the Error Log to dismiss all visible (non-dismissed) errors for the selected account at once. This is useful after resolving an underlying issue that caused many errors.

Refresh

Click the Refresh button to reload the error list with the latest data.

Common Error Scenarios and Solutions

"Connection refused" or "timeout" errors

Cause: FastBound's API is temporarily unavailable or your network connection is disrupted. Solution: Wait a few minutes and retry the operation. If persistent, check FastBound's status page and verify your API key is still valid.

"Invalid API key" or "Unauthorized"

Cause: The API key stored in Orderwerks is no longer valid. Solution: Edit the account in Business > Integrations > FastBound, enter a new API key, test the connection, and save.

"Serial format validation failed"

Cause: An imported serial number doesn't match your configured Serial Format Pattern. Solution: Review the rejected serial. Either update the serial in FastBound to match your pattern, or adjust the pattern in Account Configuration to accept the format.

"Disposition creation failed"

Cause: Missing required data for the disposition (e.g., no contact linked, invalid item reference). Solution: View the error details to identify the specific issue. Verify the order has all required data and that the items exist in FastBound.

"Rate limit exceeded"

Cause: Too many API requests sent to FastBound in a short period. Solution: Wait a few minutes before retrying. Consider staggering large sync operations.

Pagination

The Error Log is paginated with 25 entries per page by default. Use the pagination bar at the bottom to navigate through older errors.