> For the complete documentation index, see [llms.txt](https://docs.licensespring.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.licensespring.com/events-api/event-list/troubleshooting-events.md).

# Troubleshooting Events

Resolve common Events API delivery, ordering, and consumption event issues.

Use this guide to diagnose common Events API behavior. Each entry explains the cause and the appropriate response.

{% hint style="info" %}
Webhook deliveries are not retried automatically. Review and resend failed deliveries from **Settings > Webhooks**.
{% endhint %}

### Event delivery and behavior

| Issue                                                       | Cause                                                                                                 | Resolution                                                                                                                 |
| ----------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| My endpoint missed an event                                 | Your endpoint was unavailable, returned an error, or exceeded 20 seconds. Deliveries are not retried. | Review the endpoint history in **Settings > Webhooks**, then resend the event.                                             |
| I received the same event twice                             | The event was resent, or it was rarely redelivered.                                                   | Ignore an event `id` you already processed.                                                                                |
| Events arrive out of order                                  | Events have no delivery order.                                                                        | Use `ts` and event data. Do not rely on arrival order.                                                                     |
| I changed something and got no event                        | Imports, action side effects, and some platform screens do not send events.                           | Check the event page's **Not sent when** list.                                                                             |
| I receive many `license.checked` events                     | This event is sent for every license check.                                                           | Unsubscribe if you do not need it.                                                                                         |
| I receive `scheduled_update.will_process_1_day` repeatedly  | It is sent hourly during the 24 hours before the update.                                              | Process each scheduled update `id` once.                                                                                   |
| `license.activated` arrives for an active device            | It is sent for every successful activation call.                                                      | Track `hardware_id` per license if you only need new activations.                                                          |
| Vendor platform feature changes send no event               | The license page feature editor does not send license feature events.                                 | See [License feature events](https://docs.licensespring.com/events-api/event-list/license-feature-events.md).              |
| I cannot find the feature in `data.license_product_feature` | The key depends on the event trigger.                                                                 | See the table in [License feature events](https://docs.licensespring.com/events-api/event-list/license-feature-events.md). |
| No event is sent when a product is deleted                  | Products are archived, not deleted.                                                                   | Handle `product.updated` with `is_archived: true`.                                                                         |

### Consumption events

{% hint style="warning" %}
Choose one event stream for pooled consumption billing. Counting both streams duplicates usage.
{% endhint %}

| Issue                                                    | Cause                                                                                                          | Resolution                                                                                                                                                                                     |
| -------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Usage is counted twice in billing                        | A pooled consumption sends a member event and `consumption_pool.consumption_added`.                            | Count only one stream. See [Consumption pool and offline checkout events](https://docs.licensespring.com/events-api/event-list/consumption-pool-and-offline-checkout-events.md).               |
| I never receive `*_max_reached`, but the license is full | The request exceeding the limit was rejected. Totals never reached the limit. Rejected requests send no event. | Treat `license_not_enough_consumptions`, `feature_not_enough_consumptions`, and `pool_quota_exhausted` as “limit reached” in your application.                                                 |
| I receive `*_max_reached` more than once                 | The total decreased through negative consumption or a reset, then reached the limit again.                     | This is expected. Deduplicate within your billing period if needed.                                                                                                                            |
| No `*_max_reached` for a license with overages           | The license is unlimited. Overages are allowed when `max_overages` is `0`.                                     | Set `max_overages`, or monitor `consumption_pool.*` or `license.updated`.                                                                                                                      |
| A pooled device's usage has no pool event                | The device used units reserved through an offline checkout. The pool was charged at reservation.               | This is expected. Use `consumption_pool_license_checkout.checked_out` and `.synced` to follow the pool.                                                                                        |
| The license total is lower than expected                 | Values in the `license` section are read at request start.                                                     | Use `consumption_info.consumptions`, the `consumption_pool` total, or `license.updated`. See [Event data objects](https://docs.licensespring.com/events-api/event-list/event-data-objects.md). |
| A retried call sent no events                            | The retry used the same `Idempotency-Key` and was replayed.                                                    | This is expected. The first call sent the events.                                                                                                                                              |
| A new consumption returned an old response               | The `Idempotency-Key` was reused.                                                                              | Create a new key for each consumption. See [Retrying consumption calls safely](https://docs.licensespring.com/license-api/consumption/retrying-consumption-calls-safely.md).                   |
| No event is sent when a pool period ends                 | Only manual resets send `consumption_pool.reset`.                                                              | Track the pool consumption period in your application.                                                                                                                                         |
| `missing_company_feature_flag` (403) on Add Consumption  | The license or feature is in a pool, but consumption pools are not enabled on your account.                    | Enable consumption pools on your account.                                                                                                                                                      |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.licensespring.com/events-api/event-list/troubleshooting-events.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
