Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.logbrew.co/llms.txt

Use this file to discover all available pages before exploring further.

Resolve sync keeps LogBrew and your connected tools in agreement. When you mark an event resolved in LogBrew, the app immediately resolves it in the original provider. No need to open Sentry, Linear, or any other tab. When a teammate resolves an issue on their end, LogBrew picks up that change automatically and updates the event in your feed. You always see a single, accurate resolved state across every tool you use.

​
How to resolve an event

There are two ways to resolve an event:
1

From the event detail screen

Tap any event in your feed to open the detail view, then tap the Resolve button. LogBrew contacts the provider, waits for confirmation, and marks the event resolved in your feed.
2

With a swipe action

Swipe left on any feed row to reveal the quick action menu, then tap Resolve. This is the fastest path when you want to clear several events in a row.
LogBrew uses a provider-first approach: it contacts the provider before updating your local feed. If the provider returns an error (for example, a 5xx response because it is temporarily down), LogBrew shows an error message and leaves the event unresolved in your feed. This prevents your feed from showing a resolved state that does not match reality.

​
Supported providers

https://svgl.app/library/sentry.svg

Sentry

Full two-way sync. Resolve or reopen Sentry issues from LogBrew. Webhook updates flow back automatically when issues are resolved by teammates in Sentry.
https://svgl.app/library/linear.svg

Linear

Full two-way sync. Requires the write OAuth scope. If you connected Linear before write scope was available, reconnect from Settings to upgrade permissions.
https://svgl.app/library/vercel_dark.svg

Vercel

Read-only status reflection. Deployment state changes in Vercel appear in LogBrew, but there is no resolve action for Vercel events.
https://svgl.app/library/railway_dark.svg

Railway

Deployment status sync. LogBrew reflects Railway deployment state (building, deployed, failed, crashed) from webhooks. Resolve actions are not available for Railway events.
PostHog and Stripe events are also synced into your feed, but resolve actions are not available for those providers in the current version.

​
How incoming syncs work

You do not need to do anything to receive resolve updates from teammates. When a Sentry issue is resolved directly in Sentry, by a teammate, an automation rule, or the Sentry merge queue, LogBrew receives a webhook and updates the event’s resolved state in your feed. The same applies to Linear: resolving or canceling an issue in Linear propagates back to LogBrew automatically.

​
Resolved events in the feed

By default, resolved events are filtered out of the main feed view to keep it focused on things that need attention. To view resolved events:
  1. Tap the filter icon in the Feed tab.
  2. Toggle Show resolved on.
Resolved events appear with a muted style to distinguish them from active ones.
The provider was unavailable at that moment. LogBrew did not mark the event resolved. Tap Resolve again once the provider recovers. If errors persist, check that your integration is still connected in Settings, Integrations.
Linear resolve requires the write OAuth scope. If you see an upgrade banner in the Linear integration settings, tap it to re-authorize and grant the additional permission.
Incoming resolve syncs are driven by Sentry webhooks. In the rare case a webhook is missed, LogBrew runs a background reconciler that detects drift and corrects the state automatically.