Skip to main content

Resync

The Resync section helps you understand message issues and recover from message failures. It shows which messages are retrying automatically, which require manual action, and what you can do next.

There are two views:

Retries - messages that have encountered an issue and will be automatically retried

Stuck - messages that have failed and can often be manually retried

When a retry succeeds, the message is removed from the retry and stuck lists. If it fails again later for a new reason, the retry counter resets and it's treated as a new issue.

Retries Main Screen​

The Retries screen lists failed messages with key details:

  • The time the issue occurred
  • Current retry status or next scheduled retry
  • Shape and hiveId
  • The issue reason and code
  • Direction (inbound or outbound)
  • Integration name

Filters allow you to narrow down the results.

Message Details View​

Selecting a message shows detailed failure information:

  • Identifiers (shape, IDs, correlationId / journeyId)
  • Failure timestamp
  • Retry count
  • Next retry availability
  • Error code and explanation
  • Full JSON payload

Messages stuck for 2 weeks are deleted automatically

Deleted messages disappear from Resync and dashboard metrics