Conversation
Add the Generate postmortem workflow action as a generation path, and note that AI-generated template variables populate only for postmortems generated from the Post-Incident tab. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Contributor
Preview links (active after the
|
buraizu
reviewed
Sep 15, 2026
buraizu
left a comment
buraizu
left a comment
Collaborator
There was a problem hiding this comment.
Looks good overall, left one minor suggestion and a question
Comment on lines
+53
to
+59
| ### Generate a postmortem with Workflow Automation | ||
|
|
||
| You can also generate a postmortem from a [workflow][5] using the **Generate postmortem** action. The action takes an incident and a postmortem template, and attaches the resulting postmortem to that incident. Use this path to create postmortems as part of an automated post-incident process, such as after an incident moves to resolved. | ||
|
|
||
| <div class="alert alert-warning">The AI-generated variables available to postmortem templates, such as <code>{{incident.ai_summary}}</code>, populate only for postmortems generated from the <strong>Post-Incident</strong> tab. A postmortem generated through the <strong>Generate postmortem</strong> workflow action renders these variables empty. To include AI-generated content, generate the postmortem from the <strong>Post-Incident</strong> tab.</div> | ||
|
|
||
| For the full list of variables available to postmortem templates, see [Templates][4] and [Incident variables][6]. |
Collaborator
There was a problem hiding this comment.
Just flagging that the new Generate a postmortem with Workflow Automation section is placed after the After generating a postmortem content and right before View and edit a postmortem. Do you think it might be helpful for readers if both generation options are covered before moving on to After steps and viewing and editing options?
|
|
||
| ### Generate a postmortem with Workflow Automation | ||
|
|
||
| You can also generate a postmortem from a [workflow][5] using the **Generate postmortem** action. The action takes an incident and a postmortem template, and attaches the resulting postmortem to that incident. Use this path to create postmortems as part of an automated post-incident process, such as after an incident moves to resolved. |
Collaborator
There was a problem hiding this comment.
Suggested change
| You can also generate a postmortem from a [workflow][5] using the **Generate postmortem** action. The action takes an incident and a postmortem template, and attaches the resulting postmortem to that incident. Use this path to create postmortems as part of an automated post-incident process, such as after an incident moves to resolved. | |
| You can also generate a postmortem from a [workflow][5] using the **Generate postmortem** action. The action takes an incident and a postmortem template, and attaches the resulting postmortem to that incident. Use this path to create postmortems as part of an automated post-incident process, such as after an incident is resolved. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add the Generate postmortem workflow action as a generation path, and note that AI-generated template variables populate only for postmortems generated from the Post-Incident tab.
https://datadoghq.atlassian.net/browse/DOCS-15280
What does this PR do? What is the motivation?
Merge readiness