Issue Summary

Hello team,
The Statuspage is not rendering correctly when an incident is created with a specific content structure.

This is reproducible on Data Center: (yes) / (no)
Yes

Steps to Reproduce

1. Create a new Incident. with title

   Some Quickstart transformations are failing with “Trying to create view <view name> but it currently exists as a table”
   

1. Then move the incident status to Identified and for the update message use the following text:

   Our engineers are investigating this issue. If you are effected you will see the following error in your transformation logs 
   
   
"trying to create view <view name> but it currently exists as a table. Either drop <table name> or run dbt with --full-refresh and dbt will drop it for you"
   
   To resolve immediately, run a full refresh by: 
   1.) Opening your transformation dashboard.
   2.) Clicking on a transformation name to navigate to your transformation model page.
   3.) Clicking the arrow beside the “Run” button in the top right corner and then click “Run with full refresh”.
   

       3. Once identified the external look of the page will be with broken markup.

Expected Results

Statuspage view should be normal without any issues

Actual Results

The Statuspage external view looks broken with elaborated Components data making it hard to follow/read the page.
On web page inspections, the' components section` is rendered inside the `unresolved-incidents` section instead of the `container`, which completely breaks the markup and makes the page unreadable.

Workaround

As a workaround, it is recommended to perform the page updates without the "<>" symbols until a solution is made available. I have removed the "<>" values and the page rendering is happening normally. This is likely due to the way web browsers interpret these characters and this information may have been assumed as HTML tags causing the issues to page rendering.