Email contact@firnity.com when the available recovery steps do not resolve the problem.

What to include

  • What you expected Firnity Discord for Confluence to do and what happened instead.
  • The exact visible error or status.
  • The approximate time of the problem, including your timezone.
  • Whether you were using Global Settings, Space Settings, or a Discord command or action.
  • Whether the affected destination shows Needs access, Unavailable, or another health message.
  • The name of the affected rule, summary, page list, command, or panel, when relevant.

What not to include

Do not send passwords, Discord bot tokens, authentication headers, billing details, or private Confluence page content. If a screenshot is useful, crop unrelated personal or customer information before attaching it.

Prevent duplicate writes

If Firnity Discord for Confluence records a failed send, check the destination before trying again because the message may already exist. If Confluence confirms that a page was created but a follow-up step failed, use the existing page rather than creating a duplicate.