# Live updates, toasts, and connection banners

Strive uses immediate feedback for your actions and live notifications for saved activity. A toast can acknowledge that an operation was requested before the operation finishes.

## Follow the right state

For a workflow, inspect the run. For app start or stop, inspect its lifecycle operation. For a file transfer, inspect the storage job. These saved states are more useful than whether a toast appeared or how long it remained visible.

Your actions can produce immediate feedback while other people's actions appear in shared activity or your inbox without every update becoming a toast. Opening the workspace can load existing unread items without replaying all of them as new popups.

## A stale-stream banner

The workspace can show a banner when live delivery is interrupted. Check connectivity and any sign-in prompt, then reconnect or refresh. The banner concerns the update channel; an operation can still be running or completed.

If a change is time-sensitive, open its resource and read the latest saved state. Do not submit another write solely because its live confirmation did not arrive.

## When the status is uncertain

Read the operation's history or receipt. A request can succeed while the browser loses the response. Repeating a resource-consuming or external action may have additional effects. Follow [uncertain outcomes](/docs/troubleshooting/uncertain-outcomes) before retrying.

If notifications repeatedly fail to arrive, an administrator can inspect delivery failures separately from the business operation. See [notification delivery](/docs/administration/notification-delivery).