Fix a Suspended or Pending PTO Workflow in SharePoint Designer 2013
Question details
Troubleshoot a PTO workflow that was suspended after task-list fields were removed and later remained pending with a RelatedItemManager error.
- Product
- SharePoint Designer 2013 and SharePoint workflows
- Device & OS
- not provided
- Scenario
- A PTO approval workflow creates tasks in a SharePoint task list and sends email notifications.
- Observed behavior
- The workflow was suspended with an OutcomeFieldName error. After task fields were restored, it remained pending, sent no emails, and reported an HTTP 500 RelatedItemManager error indicating that the item does not support related items.
Identify the workflow's task list and platform, and collect the full error message and any correlation ID from the workflow status page. If you use SharePoint Online, check Microsoft's current retirement guidance for SharePoint 2013 workflows before rebuilding.
Restore and verify the workflow task-list fields
Use this approach when the workflow was suspended after task-list columns were removed or reports an OutcomeFieldName error.
Open the workflow's task list in SharePoint, then select Settings > List settings and review its columns and content types.
Compare the task list with a working workflow task list, including fields such as Outcome and Task Outcome. Restore the required configuration where possible; check internal field names and content-type associations rather than relying only on display names.
Open the site in SharePoint Designer 2013, select Workflows, and open the PTO workflow. Verify the platform and the task list used by its task actions.
Select Publish in SharePoint Designer, start a new test workflow instance, and open its workflow status page to check whether it creates a task and sends the expected email.

Test the workflow with a new task list
Use a new list and a simple workflow to isolate a damaged or incompatible task-list configuration.
Investigate the RelatedItemManager HTTP 500 error
Use this approach if the workflow starts but remains pending and reports that the task item does not support related items.
Track PTO requests in a WPS Office spreadsheet
WPS Office is a free, lightweight Office alternative with a familiar interface. Open existing Microsoft Office files to maintain a manual PTO tracker while your SharePoint workflow is investigated. WPS does not repair or run SharePoint workflows.

Frequently Asked Questions
Why did the workflow become suspended after task fields were deleted?
The workflow may depend on task outcome fields and their content-type configuration. Open the task list's Settings > List settings and compare its fields with a working workflow task list.
Why is the workflow still pending after I restored the outcome fields?
Restoring the fields may clear the original suspension without fixing a separate error. Check the workflow status page for the latest message, particularly a RelatedItemManager HTTP 500 error.
How can I tell whether the task list is causing the problem?
Create a new workflow-compatible task list from Settings > Add an app, then publish and run a simple workflow against it. If the test works, compare its list settings and content types with the original list.
Will enabling workflow app permissions fix the RelatedItemManager error?
Not necessarily. An error saying the item does not support related items can indicate a task-item or list configuration issue. Collect the error and correlation ID from the workflow status page and ask a SharePoint administrator or Microsoft support to investigate.
Can WPS Office repair a SharePoint workflow?
No. WPS Office cannot repair or run SharePoint workflows, but WPS Spreadsheets can open an XLSX file for manual PTO tracking while the workflow is investigated.




