When incident is proposed as Major incident via MI Trigger Rule, the "Major Incident" section on Incident form displays sometimes after refreshing the form. Issue <!-- div.margin { padding: 10px 40px 40px 30px; } table.tocTable { border: 1px solid; border-color: #e0e0e0; background-color: #fff; } .title { color: #d1232b; font-weight: normal; font-size: 28px; } h1 { color: #d1232b; font-weight: normal; font-size: 21px; margin-bottom: 5px; border-bottom-width: 2px; border-bottom-style: solid; border-bottom-color: #cccccc; } h2 { color: #646464; font-weight: bold; font-size: 18px; } h3 { color: #000000; font-weight: bold; font-size: 16px; } h4 { color: #666666; font-weight: bold; font-size: 15px; } h5 { color: #000000; font-weight: bold; font-size: 13px; } h6 { color: #000000; font-weight: bold; font-size:14px; } ul, ol { margin-left: 0; list-style-position: outside; } --> Overview When Major Incident Trigger Rules are used to make an incident as a Major Incident candidate, then the "Major Incident" section on form sometimes appears after the refreshing the form. Justification This is the expected behavior of this feature. Major Incident Trigger Rule get evaluated via an OOB Async Business rule "Evaluate Major Incident Trigger Async". Async BR runs when the scheduler runs the scheduled job created from the business rule. The system creates a scheduled job from the business rule after the user submits the form and after any action is taken on the record in the database. Once the scheduled job is processed, then the MI Trigger rule logic is processed after which the UI policy to display the section works. Therefore, the "Major Incident" section on the form shows up sometimes after refreshing the form and not immediately. Additional Information Create trigger rules for major incidentsHow business rules work