Help Center / Developers
When should I use SeleKV or SeleQueue?
Use the SeleKV documentation to evaluate simple key-value reads such as settings and caches.
Use the SeleKV documentation to evaluate simple key-value reads such as settings and caches. Use the SeleQueue documentation to evaluate background work that can run after the original request. Plan how the app handles expired data, retried jobs and failures before relying on either service.
Before you start
Decide whether the workload is a lookup or deferred work.
What to do
For caches, define expiry and a source of truth. For jobs, give retries a stable job identity and record results.
Common problems
If a job repeats, check its retry history and whether the handler safely recognizes work it already completed.
Last updated November 12, 2026.
Frequently asked questions
What should I check first for SeleKV or SeleQueue?
Decide whether the workload is a lookup or deferred work. For caches, define expiry and a source of truth. For jobs, give retries a stable job identity and record results. If a job repeats, check its retry history and whether the handler safely recognizes work it already completed.
What should I do if I get stuck with SeleKV or SeleQueue?
If a job repeats, check its retry history and whether the handler safely recognizes work it already completed. Decide whether the workload is a lookup or deferred work. If you need help, include the product you were using and the step that failed. Keep passwords, one-time codes and secret keys private.
When should I use SeleKV or SeleQueue?
Use the SeleKV documentation to evaluate simple key-value reads such as settings and caches. Use the SeleQueue documentation to evaluate background work that can run after the original request. Plan how the app handles expired data, retried jobs and failures before relying on either service.
Keep reading
Still need help?
Open the app and tap the chat icon at the top, or choose Help and Support from the menu, to create a ticket or start live chat.
SeleID Help
