How the management app handles offline actions (the outbox)
Signal drops — in a stockroom, a basement, a rural branch. The RushFlow management app keeps working: actions you take offline (like recording an expense) are saved to a local outbox and submitted automatically the moment you’re back online. Crucially, if the server rejects a queued action on replay, it isn’t silently dropped — it moves to a failed-sync review queue so you can see it, fix it, retry or discard it. Nothing you created offline disappears.
Step by step
- Work as normal offlineApp: record the expense or action even with no connection. The app confirms it’s saved locally and shows a pending/outbox count.
- Let it sync automaticallyWhen the connection returns, the outbox replays its queued actions to the server in order — you don’t have to do anything.
- Check the failed-sync queue if promptedIf the server rejects an action (e.g. a value that’s no longer valid), it lands in the failed sync review screen with a failed count badge.
- Retry or discardIn the failed-sync screen, Retry re-queues the action (all at once or one at a time), or Discard removes it after you confirm — your choice, never automatic.
Why a dead-letter queue matters
Most “offline” apps either lose a rejected write or jam the whole queue behind it. RushFlow separates the two: good actions sync, and rejected ones wait for you in a clearly labelled review list — so one bad record never blocks the rest and nothing goes missing.
Frequently asked questions
Can I use the management app without internet?
Yes. Actions you take offline are saved to a local outbox and submitted automatically when you reconnect.
What happens if a synced action is rejected by the server?
It moves to a failed-sync review queue with a badge count. You can retry it (all or one) or discard it after confirming — it is never silently dropped.
Ready to run your business on RushFlow?
Start a free trial, or explore the live demo — no credit card needed.
Create your account →