Source: https://dinakar-pageloop-knowledge-base.docs-staging.pageloop.ai/faq

# FAQ

# FAQ

#### Does a 201 mean my endpoint received the event?

No. `201` means Kestrel durably stored the event and will attempt delivery. Check
`GET /v1/deliveries?eventId=…` for what actually happened.

#### Can I get events in order?

Yes, per endpoint, if you publish with the same `streamKey`. Ordering is not global
and does not hold across different keys. See [Events](/concepts/events).

#### Why am I receiving the same event twice?

A retry reuses the event `id`, so a response lost after you processed it produces a
duplicate. Deduplicate on `id` with a 24-hour window — see
[Delivery and retries](/concepts/delivery-and-retries).

#### What happens to events while my endpoint is down?

Each delivery is retried 5 times over roughly a minute, then marked `exhausted`. The
event stays in your retention window and can be replayed once you are back.

#### Can I change my account's region?

No. Region is fixed at account creation. See [Regions](/reference/regions).

#### Do you have a sandbox?

Test-mode keys (`sk_test_…`) operate on an isolated dataset and never deliver to
production subscriptions. There is no separate host.

#### How do I rotate a signing secret without dropping deliveries?

Rotation keeps the previous secret valid for 24 hours. Verify against both during the
overlap. See [Signatures](/concepts/signatures).

#### Is there a way to filter which events reach an endpoint?

Subscriptions match on event type, including a trailing-segment wildcard. There is no
payload-content filtering — do that in your handler.

## Still stuck?

- [Limits and quotas](/reference/limits-and-quotas)

  Every hard number in one table.
- [Handling failures](/guides/handling-failures)

  The triage playbook.