# Change notifications

Choose between transient application notifications and durable change delivery.

Source: https://particledb.ai/connectivity/changefeeds/

Notifications and durable change feeds solve different problems. A connected client receiving an event does not establish replay after a disconnect.

## Before selecting an API

Verify that your release supports the intended subscription command or streaming endpoint. Check authentication, ordering, reconnection behavior, buffering and backpressure.

## For durable workflows

Record pending work in a table as part of the application transaction. A worker can read that state and update its progress. Use stable identifiers and explicit retry handling.

Do not describe a transient notification as a durable queue or promise that a disconnected consumer receives every event.

[Agent and workflow patterns](/guides/agents-and-workflows/) · [Transactions](/sql/transactions/)

## Related

[Documentation home](/docs/) · [Troubleshooting](/guides/troubleshooting/)
