Notika for...
FAQ
Get answers to frequently asked questions about Notika.
Your database should be the source of truth for your application state. If you find yourself needing to track events outside the database, consider extending your data model to capture these state changes.
For example, with user onboarding, you could add an onboarding_status column to track completion state directly in your users table.
To ensure robustness around transient errors (for instance, if your database is unavailable due to network connectivity issues), Notika automatically retries failed workflow steps with exponential backoff.
If a workflow fails after exhausting all retries, it will be marked as failed and you will be notified.
We have an entire section dedicated to this topic here.
There are several strategies to ensure that your Notika workflows stay intact as you make changes to your database schema.
Notika depends on your data store to function. If your database is fully unresponsive, your workflows will not be able to run.
If your database network is spotty, events will continue to accrue, and no events will be lost. Workflow steps will simply retry if a network error is encountered.
Was this page helpful?