Skip to main content
Documentation
Documentation
Adaptive Planning
Last Updated: 2026-05-15
Troubleshooting: Advanced Workflows

Troubleshooting: Advanced Workflows

Something isn’t working or not displaying.

When something goes wrong, we recommend that you check for these causes first before you continue troubleshooting.
You didn’t enable the Configurable Workflows feature.
You didn’t ensure that your access rules include you and your workflow participants.
For submit and approve tasks and hierarchy submit tasks, you didn’t edit your associations to include level owners for all participating levels.
Users can’t see the hub because you didn’t share the hub with those users or give them the
Access Hubs
 permission.
Users can’t see the
Workflows
 section in the hub because they don’t have the
Manage Workflows
 permission.

The Publish button is disabled on my workflow definition even though it looks like I added everything.

Your workflow definition includes a mixture of both:
  • Tasks that have a task duration.
  • Tasks that don’t have a task duration.
Task durations are optional, but we only support workflow definitions where either:
  • All tasks have a task duration.
  • No tasks have a task duration.
Security:
Manage Workflows
 permission.
  1. Manually review the
    Task Duration
     field on every task in this workflow definition to check whether or not you entered a task duration.
  2. Either:
    • Enter a task duration on all tasks.
    • Remove the task duration from all tasks.
The submit and approve tasks on your workflow definition uses the same associations.
Assign different associations for submit and approve tasks that exist in 1 group.
Example: You create these associations: HR Submitter, HR Approver, and HR secondary approver. For a task group that includes 1 submit task and 2 approve tasks, you can’t assign all tasks to HR Approvers. Instead, assign HR Submitter to the submit task, and assign HR Approver to the approve task and HR secondary approver to the 2nd approve task.

Workflow participants can’t take action on their workflow tasks.

Many possible reasons exist. Examples:
  • Your access rules don’t currently allow those users to access the data that they need to see.
  • You didn’t share the hub with them.
  • The user no longer has the
    Access Hubs
     permission.
  • Those users don’t have access to the underlying asset.
  • The level is no longer available to that user.
  • The workflow administrator paused the workflow.
Ask your workflow participant to tell you what the error message said, and troubleshoot the cause of that issue.

My workflow definition and workflow show the error info icon and tooltip.

Some system changes and ongoing business operations can impact your workflow definitions or workflows. Examples:
  • You changed your associations and users. These changes can include:
    • A participating level no longer has an assignee associated if you don’t select
      Auto-select and maintain valid descendants
       on the workflow. When you select
      Auto-select and maintain valid descendants
      , we automatically remove invalid levels.
    • You deleted users so that level owners no longer exist for your participating levels.
    • You deleted users that are assigned to a to-do task and now that to-do task is blocked from being completed because no user is assigned.
  • You deleted a task destination.
  • You deleted levels that are participating in the workflow or made the levels unavailable on the version. Those were the only participating levels for that workflow and the workflow cannot proceed because of this.
We display error messages throughout to tell you how to fix those errors. Sometimes we send a notification to your administrators when errors happen so that they can fix them.
To view workflow errors and start troubleshooting them, edit your workflow.
To fix errors related to associations, either:
  • Edit your workflow and update the participating levels.
  • Update your associations.
To fix errors related to users breaking the workflow definition or if only 1 user exists in a user group, either:
  • Update the workflow definition to assign that 1 user instead of the user group.
  • Update the user group and add additional users.