---
title: Frequently Asked Questions (FAQs)
description: Most frequently asked questions.
documentId: events-hub-faqs
locale: en-US
---

<Accordion title="Does Events Hub guarantee event delivery?">
Yes. Through confirmation mechanisms and flow control, Events Hub ensures that events are correctly delivered to recipients.
</Accordion>

<Accordion title="In case of failure, how long are events available for resending to subscribers?">
Events remain available on the [Delivery Retry](/docs/events-hub/delivery-retry) screen for 14 days.
</Accordion>

<Accordion title="What is the difference between automatic and manual retry?">
When the first attempt to deliver an event to a subscriber fails, Events Hub tries to [automatically resend](/docs/events-hub/policies#automatic-delivery-retries) it, following the settings registered in the [policy](/docs/events-hub/policies).
If all automatic attempts fail, the event moves to the retry queue on the *Delivery Retry* screen, where you can [manually retry](/docs/events-hub/delivery-retry#manual-retry) it.
</Accordion>

<Accordion title="Can I schedule retries automatically?">
Yes. Through the [Event Status](/docs/events-hub/delivery-retry#automatic-retry) API, you can implement automation to automatically resend events from the manual retry queue.
</Accordion>

<Accordion title="How does Events Hub enable the event publishing URL?">
The URL is formed by `Base URL` + `context` + `handler` + `topic`:

- **Base URL**: defined by **Events Hub**. It includes the address of each client's interface + `event-receiver` + a unique code (hash).

- **Context**, **handler**, and **topic**: created by you. They help organize and manage different publishing channels.

    - **Topic** is the most specific level.

    - **Handlers** aggregate topics, serving as a logical grouping layer.

    - **Contexts** add another grouping level, allowing the same topic to be used in different situations.
</Accordion>

<Accordion title="Do I need to configure the authorization URL for events to be sent?">
If you add [policies](/docs/events-hub/policies) to your handler, yes. You will need to configure the authorization URL linked to the interceptor.
With the exception of "IP Filtering Validation," all depend on this configuration to function.

<Callout type="NOTE" title="NOTE">
Access the [Authorizations](docs/events-hub/authorizations#obtaining-the-authorization-URL-using-the-sensedia-API-platform) documentation to see how to configure them using the *Sensedia API Platform*.
</Callout>
</Accordion>

<Accordion title="Do I need to use the Sensedia API Platform as an authorization server?">
No. Events Hub accepts any authorization URL to validate event policies.
</Accordion>