Hi,
but not through standard Advanced Filter/Sort in the Workflow history page. In D365FO, the workflow error text is stored in:
WorkflowTrackingCommentTable.TrackingMessage
Related workflow instance/header data is in:
WorkflowTrackingTable
WorkflowTrackingStatusTable
Microsoft’s CDM docs confirm these tables/fields exist: WorkflowTrackingCommentTable in Framework - Common Data Model - Common Data Model | Microsoft Learn,
WorkflowTrackingTable in Framework - Common Data Model - Common Data Model | Microsoft Learn and
WorkflowTrackingStatusTable in Framework - Common Data Model - Common Data Model | Microsoft Learn
Exact D365FO solution
Create a small custom inquiry form, report, or runnable class that searches WorkflowTrackingCommentTable.TrackingMessage.
Example runnable class:
class YourClassName
{
public static void main(Args _args)
{
WorkflowTrackingCommentTable commentTable;
WorkflowTrackingTable trackingTable;
WorkflowTrackingStatusTable statusTable;
str searchText = "budget exceeded";
while select commentTable
where commentTable.TrackingMessage like strFmt("*%1*", searchText)
|| commentTable.Comment like strFmt("*%1*", searchText)
join trackingTable
where trackingTable.RecId == commentTable.WorkflowTrackingTable
join statusTable
where statusTable.RecId == trackingTable.WorkflowTrackingStatusTable
{
info(strFmt(
"Company: %1 | Instance: %2 | Workflow: %3 | Document: %4 | Originator: %5 | Message: %6",
statusTable.ContextCompanyId,
statusTable.InstanceNumber,
statusTable.ConfigurationName,
statusTable.Document,
statusTable.Originator,
commentTable.TrackingMessage));
}
}
}
For production use, make this a custom inquiry form with a search field for error text, plus filters for company, workflow name, document, originator, and date. Do not rely on Advanced Filter/Sort for this, because the visible workflow history message is not exposed in the standard form as a simple searchable datasource field.
To fix specific failed workflows after finding them:
- Go to Common > Inquiries > Workflow > Workflow history.
- Search by the returned Instance number, Document, or Workflow.
- Open the failed workflow and check the tracking details.
- Fix the root cause, for example missing security role, invalid approval hierarchy, budget control issue, stopped batch, or custom X++ exception.
- Recall/resubmit or resume/retry the workflow depending on the document type and workflow status.
standard UI does not provide a direct “search workflow history by error message” feature. The exact technical place to search is WorkflowTrackingCommentTable.TrackingMessage, joined back to WorkflowTrackingTable and WorkflowTrackingStatusTable
Thanks!
If you found it helpful, please consider marking it as Verified — it may be useful for others in the future!
