---
title: "Troubleshooting"
canonical_url: "https://apidocs.sportradar.com/resources/widgets/docs/custom-bet/troubleshooting"
markdown_url: "https://apidocs.sportradar.com/resources/widgets/docs/custom-bet/troubleshooting.md"
last_updated: "2026-03-23T18:44:01Z"
---

# Troubleshooting

This section provides guidance for common issues encountered when working with the Custom Bet widget.

### Debug Mode

The widget provides a `dbg` prop that can be set to `true` to get some extra information on markets and outcomes, which can be useful in development or debugging sessions. This prop is meant to be used in development environments only.

### Match Not Supported

Depending on your integration you can handle match not supported in two different ways, either by hiding the widget or by showing a message in the widget.

To show a "match not found" message inside the widget, return a general error from the [`getOfferingCallback`](https://apidocs.sportradar.com/resources/widgets/docs/custom-bet/integration/data-adapter.md#getofferingcallback) with empty markets, and return empty [`cbMarkets`](https://apidocs.sportradar.com/resources/widgets/docs/custom-bet/integration/data-adapter.md#calculationmarket) from the [`calculateCallback`](https://apidocs.sportradar.com/resources/widgets/docs/custom-bet/integration/data-adapter.md#calculatecallback):

<img src="/img/customBet.matchNotFound.png" width="500" alt="Match Not Found" />

**`getOffering` callback:**

```javascript
callback(
  {
    type: 1, // general error
    message: "Match not found",
  },
  {
    matchName: "FC Home vs FC Away",
    markets: [],
    marketCategories: [],
  },
);
```

**`calculate` callback:**

```javascript
callback(undefined, {
  cbMarkets: [],
});
```

## Additional Resources

For more general troubleshooting information, see the [troubleshooting guide](https://apidocs.sportradar.com/resources/widgets/docs/tutorials/troubleshooting.md).