Skip to content
Open
Show file tree
Hide file tree
Changes from 5 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion source/deployment-guide/mobile/mobile-troubleshooting.rst
Original file line number Diff line number Diff line change
Expand Up @@ -143,8 +143,13 @@ If you did not receive a push notification when testing push notifications, use
- If the log message displays, it means a message was sent to the HPNS server and was not received by your mobile app. Please `create a support ticket <https://support.mattermost.com/hc/en-us/requests/new>`_ with the subject "HPNS issue" for help from Mattermost's Support team.
- If the log message does not display, it means no mobile push notification was sent to “Account A”. Please repeat the process starting at step 2 and double-check each step.

If push notifications are not being delivered on the mobile device, confirm that you're logged in to the **Native** mobile app session through **Profile > Security > View and Log Out of Active Sessions**. Otherwise, the `DeviceId` won't get registered in the `Sessions` table and notifications won't be delivered.

.. important::

To conserve disk space, once your push notification issue is resolved, go to **System Console > Environment > Logging > File Log Level**, then select **ERROR** to switch your logging detail level from **DEBUG** to **Errors Only**.

If push notifications are not being delivered on the mobile device, confirm that you're logged in to the **Native** mobile app session through **Profile > Security > View and Log Out of Active Sessions**. Otherwise, the `DeviceId` won't get registered in the `Sessions` table and notifications won't be delivered.
Integration posts (MM Blocks) do not render or respond
-------------------------------------------------------

If buttons, menus, or structured layout content from an integration post is missing or unresponsive on mobile, see :doc:`Troubleshoot MM Blocks </get-help/mm-blocks-troubleshooting>`.
4 changes: 4 additions & 0 deletions source/end-user-guide/access/client-availability.rst
Original file line number Diff line number Diff line change
Expand Up @@ -147,6 +147,8 @@ Integrations
+-----------------------------------------------------------------------------------------------------------------+-------------+-------------+-----------------+
| `Outgoing webhooks <https://developers.mattermost.com/integrate/webhooks/outgoing/>`_ | |checkmark| | |checkmark| | |checkmark| |
+-----------------------------------------------------------------------------------------------------------------+-------------+-------------+-----------------+
| :doc:`MM Blocks </integrations-guide/mm-blocks>` [1]_ | Conditional | Conditional | Conditional |
+-----------------------------------------------------------------------------------------------------------------+-------------+-------------+-----------------+
| `Message attachments <https://developers.mattermost.com/integrate/reference/message-attachments/>`_ | |checkmark| | |checkmark| | |checkmark| |
+-----------------------------------------------------------------------------------------------------------------+-------------+-------------+-----------------+
| `Message buttons <https://developers.mattermost.com/integrate/plugins/interactive-messages/#message-buttons>`_ | |checkmark| | |checkmark| | |checkmark| |
Expand All @@ -158,6 +160,8 @@ Integrations
| `Right-hand sidebar <https://developers.mattermost.com/integrate/reference/server/server-reference/>`_ | |checkmark| | |checkmark| | |
+-----------------------------------------------------------------------------------------------------------------+-------------+-------------+-----------------+

.. [1] Requires ``MM_FEATUREFLAGS_MMBLOCKSENABLED`` to be enabled on the Mattermost server (defaults to ``true``). When set to ``false``, clients do not render native ``mm_blocks`` payloads and the server rejects MM Blocks action requests. See :doc:`MM Blocks </integrations-guide/mm-blocks>` for details.

Authentication
~~~~~~~~~~~~~~

Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -26,6 +26,44 @@ Mattermost interoperability
- :ref:`ServiceNow <integrations-guide/servicenow:use>`
- :ref:`Zoom <integrations-guide/zoom:use>`

Interact with integration messages
----------------------------------

Many integrations post rich, actionable content into channels using **MM Blocks**—a structured layout format for text, images, buttons, menus, and grouped content. You may also see the same presentation for older integrations that use message attachments; Mattermost translates those into the MM Blocks layout automatically.

What you may see in a channel
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Integration posts can include:

- **Text and images** formatted with headings, emphasis, and links.
- **Grouped content** in bordered or shaded containers, sometimes arranged in columns.
- **Buttons** labeled with actions such as *Acknowledge*, *Approve*, or *View details*.
- **Menus** (static selects) that let you choose from a list of options.
- **Collapsible sections** with a header you can tap to show or hide additional details.

Using buttons and menus
~~~~~~~~~~~~~~~~~~~~~~~

1. **Buttons:** Select a button to send your choice to the integration. The integration may update the post in place or send you a private follow-up message visible only to you.
2. **Menus:** Select the menu to open the list of options, then choose one. Mattermost sends the selected value to the integration, similar to pressing a button.
3. **Disabled controls:** Some buttons or menus appear grayed out and cannot be selected until the integration enables them.

If nothing happens after you select a button or menu option, wait a moment in case the integration is still processing. Contact your system admin if actions consistently fail.

Expandable and scrollable content
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Some integration posts clip long content to keep the channel readable.

- **Collapsible sections:** Select the section header to expand or collapse the content beneath it.
- **Web and desktop:** When a content region has a height limit, scroll inside the post to read the full content.
- **Mobile:** When content is clipped, a fade appears at the bottom of the region and an expand control is shown in the bottom-right corner. Select that control to open a full-screen **Scrollable content** view. Scroll through the complete content, then use the back gesture or navigation control to return to the channel.

.. tip::

Integration developers can learn how to build MM Blocks payloads in the :doc:`MM Blocks </integrations-guide/mm-blocks>` documentation. If content does not render or respond as expected, see :doc:`Troubleshoot MM Blocks </get-help/mm-blocks-troubleshooting>`.

.. tip::

- `Visit the Mattermost Marketplace <https://mattermost.com/marketplace/>`__ to find open source, community-supported integrations to common developer tools like `CircleCI <https://mattermost.com/marketplace/circleci/>`__, `Opsgenie <https://mattermost.com/marketplace/opsgenie/>`__, `PagerDuty Notifier <https://mattermost.com/marketplace/pagerduty/>`__; productivity tools like `Autolink <https://mattermost.com/marketplace/autolink-plugin/>`__, `ToDo <https://mattermost.com/marketplace/todo/>`__, and `WelcomeBot <https://mattermost.com/marketplace/welcomebot-plugin/>`__; as well as social tools like `Memes <https://mattermost.com/marketplace/memes-plugin/>`__ and `GIFs <https://mattermost.com/marketplace/giphy-plugin/>`__ that are freely available for use and customization.
Expand Down
2 changes: 1 addition & 1 deletion source/end-user-guide/messaging-collaboration.rst
Original file line number Diff line number Diff line change
Expand Up @@ -36,4 +36,4 @@ Getting Started
* :doc:`Communicate with messages and threads </end-user-guide/collaborate/communicate-with-messages>` Learn how to get started collaborating within Mattermost channels.
* :doc:`Collaborate within Microsoft Teams </end-user-guide/collaborate/collaborate-within-connected-microsoft-teams>` - Learn how to get started collaborating within Microsoft Teams.
* :doc:`Keyboard shortcuts </end-user-guide/collaborate/keyboard-shortcuts>` - Make a more efficient use of your keyboard with keyboard shortcuts.
* :doc:`Extend Mattermost with integrations </end-user-guide/collaborate/extend-mattermost-with-integrations>` - Find open source integrations to common tools in the Mattermost Marketplace.
* :doc:`Extend Mattermost with integrations </end-user-guide/collaborate/extend-mattermost-with-integrations>` - Find open source integrations to common tools in the Mattermost Marketplace, and learn how to interact with rich integration messages (MM Blocks).
3 changes: 3 additions & 0 deletions source/get-help/get-help-index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,7 @@ Training and Support
/get-help/community-chat.rst
/get-help/community-for-mattermost.rst
/get-help/contribute-to-documentation.rst
/get-help/mm-blocks-troubleshooting.rst

Get the help you need with Mattermost via robust documentation, extensive community support, and professional support services. If you're struggling with something on your Mattermost journey, take a look at the following learning resources:

Expand All @@ -31,6 +32,8 @@ Help Center

Visit the `Mattermost Help Center <https://support.mattermost.com/hc/en-us>`_ to access frequently asked questions and common troubleshooting tips.

- :doc:`Troubleshoot MM Blocks </get-help/mm-blocks-troubleshooting>` — Resolve rendering and interaction issues with integration posts that use MM Blocks, including expandable content on mobile.

Commercial Customer Support
---------------------------

Expand Down
77 changes: 77 additions & 0 deletions source/get-help/mm-blocks-troubleshooting.rst
Original file line number Diff line number Diff line change
@@ -0,0 +1,77 @@
Troubleshoot MM Blocks
======================

.. include:: ../_static/badges/all-commercial.rst
:start-after: :nosearch:

Integration posts that use :doc:`MM Blocks </integrations-guide/mm-blocks>` show structured content—text, images, buttons, menus, and layouts—directly in a channel. This page covers common issues when MM Blocks do not render or respond as expected, with emphasis on mobile clients.

MM Blocks content does not appear
---------------------------------

**Symptoms:** A post shows only plain text (or no content) and the expected buttons, images, or layout blocks are missing.

**Try the following:**

1. **Update your client.** MM Blocks require a current Mattermost web, desktop, or mobile app. See :doc:`client availability </end-user-guide/access/client-availability>` for platform support.
2. **Confirm the integration payload.** The post must include a non-empty ``props.mm_blocks`` array (or a legacy format such as message attachments that the client translates). Ask your integration owner or system admin to verify the webhook or bot payload.
3. **Check the feature flag (system admins).** Self-hosted deployments can disable MM Blocks by setting ``MM_FEATUREFLAGS_MMBLOCKSENABLED=false``. When disabled, native MM Blocks payloads are not rendered and their actions are rejected. See :doc:`MM Blocks </integrations-guide/mm-blocks>` for details.
4. **Reload the channel.** Pull to refresh on mobile, or switch channels and return, to fetch the latest post data.

Buttons or menus do not respond
-------------------------------

**Symptoms:** Buttons appear disabled, or tapping a button or menu option has no effect.

**Try the following:**

1. **Wait for the action to finish.** Some integrations show a loading state while Mattermost calls an external service. Slow integrations may time out based on your server's :ref:`integration request timeout <administration-guide/configure/integrations-configuration-settings:integration request timeout>` setting.
2. **Check whether the control is disabled.** Integrations can send buttons and menus in a disabled state. Disabled controls cannot be activated.
3. **Verify outbound server connectivity.** External actions require Mattermost **server nodes** (not end-user devices) to make **outbound** requests to each integration action endpoint URL configured in the post. These endpoints typically use **HTTPS on TCP port 443**; if a URL uses another scheme or port, that destination must be reachable outbound from the server. Allow only the specific integration endpoints your organization uses—this is not an inbound connection requirement.
4. **Look for follow-up messages.** Successful actions may update the original post or return an ephemeral reply visible only to you. Check the thread panel if the post is part of a thread.

Scrollable content issues on mobile
-----------------------------------

**Symptoms:** Clipped integration content cannot be expanded, or the **Scrollable content** screen is empty.

Some integration posts limit the height of a content region. When content overflows, Mattermost mobile shows a clipped preview with an expand control in the corner of the region.

**To view the full content on mobile:**

1. Locate the clipped region in the post (a fade at the bottom indicates more content below).
2. Select the expand control in the bottom-right corner of the clipped area.
3. Mattermost opens a full-screen **Scrollable content** view where you can scroll through the complete block content.
4. Use the back gesture or navigation control to return to the channel.

**If the Scrollable content screen shows "Cannot display content":**

- Return to the channel and open the expand control again. This screen appears when the expanded payload is no longer available (for example, after navigating away before the view loaded).
- Update to the latest mobile app build if the issue persists across multiple posts.

On web and desktop, the same clipped regions scroll inside the post; a separate full-screen view is not used.

Collapsible sections or images look wrong
-----------------------------------------

**Symptoms:** A section will not expand, an image fails to load, or part of the layout is missing.

**Try the following:**

1. **Collapsible sections:** Select the section header to toggle between expanded and collapsed states. If the header is missing or empty, the integration payload may be incomplete.
2. **Images:** External images require a valid URL and may be blocked by your server's image proxy or SVG settings. Contact your system admin if images from other integrations load but MM Blocks images do not.
3. **Partial content:** Clients skip individual malformed blocks and still render valid ones in the same post. If only some elements are missing, the integration payload likely contains invalid block entries.

Legacy message attachments
--------------------------

Older integrations that use `message attachments <https://developers.mattermost.com/integrate/reference/message-attachments/>`_ are translated into the MM Blocks UI at render time. Button and menu behavior should match native MM Blocks posts. If an attachment-based post behaves differently from a native MM Blocks post, report the payload to your integration owner.

Get more help
-------------

- **End users:** See :doc:`Extend Mattermost with integrations </end-user-guide/collaborate/extend-mattermost-with-integrations>` for how to use buttons, menus, and expandable content in channels.
- **Developers:** See :doc:`MM Blocks </integrations-guide/mm-blocks>` for payload format, action APIs, and migration guidance.
- **Mobile deployment issues:** See :doc:`Mobile deployment troubleshooting </deployment-guide/mobile/mobile-troubleshooting>` for connectivity, push notification, and app install problems unrelated to MM Blocks content.

If you continue to experience issues, visit the `Mattermost Troubleshooting forum <https://forum.mattermost.com/c/trouble-shoot/16>`_ or contact your system administrator.
9 changes: 8 additions & 1 deletion source/integrations-guide/faq.rst
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,14 @@ What are attachments?

When "attachments" are mentioned in Mattermost integrations documentation, it refers to Slack's message attachments functionality. These "attachments" can be optionally added as an array in the data sent by an integration, and are used to customize the formatting of the message.

Mattermost doesn't currently support the ability to attach files to a post made via webhook. You can use the API to attach files to a message if needed.
Mattermost doesn't currently support the ability to attach files to a post made via webhook. You can use the API to attach files to a message if needed.

What are MM Blocks?
--------------------

:doc:`MM Blocks </integrations-guide/mm-blocks>` are Mattermost's structured format for rich, interactive posts. Integrations set ``props.mm_blocks`` (content and controls) and ``props.mm_blocks_actions`` (integration URLs and navigation targets) on a post.

MM Blocks are the recommended way to build interactive messages with buttons, menus, images, and layouts. Legacy `message attachments <https://developers.mattermost.com/integrate/reference/message-attachments/>`_ and other formats (Slack Block Kit ``blocks``, Adaptive Cards ``cards``) are still accepted and translated into MM Blocks at render time.

Where can I find existing integrations?
---------------------------------------
Expand Down
Loading
Loading