Why is the workflow editor not loading?

The Workflow Editor is a React application loaded from the plugin’s compiled builder assets. It fetches workflow data and node types through the plugin REST API. A blank or incomplete editor can therefore have more than one cause. Check the build-asset notice first, then inspect the browser and WordPress responses.

Open the editor and confirm access

1. In the WordPress dashboard, open Agent Workflows → Workflows.
2. Use the workflow’s Edit action, or choose the add-workflow action, to open Workflow Editor.
3. Confirm the current user has the dragaiw_manage_workflows capability. The editor page and its workflow REST endpoints check this capability.

Screenshot to add: [Workflow Editor visual builder]

Separate an asset problem from a loading problem

• If the page displays the plugin notice that the builder app has not been built, follow Missing build assets. Confirm the compiled manifest and JavaScript exist in assets/builder/build/.
• If the notice is absent but the builder area is blank, open the browser developer tools and check the Console for a JavaScript exception. Read the actual message and identify the script or extension involved before changing the site.
• In the Network panel, check whether the builder JavaScript and CSS requests load successfully. A missing file or server error needs a different fix from a JavaScript runtime exception.
• Check the browser Network panel for requests to the dragaiw/v1 REST namespace. A failed request may point to permissions, a server-side error, or a response altered by a security or caching layer.
• If the editor loads but a workflow or node list is missing, check the REST response and the user’s capability before treating it as an asset problem.

Check permissions and plugin conflicts

The editor page requires dragaiw_manage_workflows. Its REST routes also check the relevant capability. Administrators with manage_options are granted the plugin capabilities by the plugin’s capability filter; custom roles need the required capability assigned through your role-management process.

• Sign in with an account that should have workflow access and confirm the workflow list and editor open.
• If the browser console and REST responses do not identify the cause, test on a staging site with other admin plugins temporarily disabled, then re-enable them one at a time.
• If you use a caching or security layer, check its logs for the specific failed asset or REST request. Do not disable production security controls broadly as a first step.
• After each change, reload the editor and compare the actual Console and Network results.

What to include in a support report

Share the plugin version, WordPress and PHP versions, the exact screen where loading stops, and a redacted Console or Network error. Remove cookies, authorization headers, API keys, and private workflow data before sharing diagnostic output. A browser error should be reported as an observed browser error, not as a message generated by the plugin unless the plugin itself displays it.