Error Messages for Flow Designer

Can’t Connect to Mule

Flow Designer can’t connect to the Runtime Manager Agent

View the log for your project, which you can do by clicking Log in the bottom-left corner of the screen. There should be an error message that indicates the reason for the failure. Then, open a support case for Runtime Manager and paste the error message into the support case.

Can’t Retrieve App (CloudHub)

You either lack permissions to retrieve applications in the current organization or the application has been deleted.

Check Runtime Manager to find out whether your application is running. If it isn’t, open a support case for Flow Designer.

Can’t Retrieve App (Project Manager)

Flow Designer failed to retrieve information about your project.

Open a support case for Flow Designer. Provide the name of your project in the support case.

Cloudhub Internal Error

CloudHub failed to process the request.

Open a support case for CloudHub.

Deployment Failed

The project couldn’t be deployed to the CloudHub worker.

View the log for your project, which you can do by clicking Log in the bottom-left corner of the screen. There should be an error message that indicates the reason for the failure, what to do to resolve the problem, or both.

Flow Can’t Be Empty

At least one of the flows in your Mule app is missing a trigger.

Find the flow or flows missing a trigger and add a trigger to each.

Mule Agent Internal Error

Flow Designer failed to deploy or to stop your mule app in the Mule runtime.

View the log for your project, which you can do by clicking Log in the bottom-left corner of the screen. There should be an error message that indicates the reason for the failure, what to do to resolve the problem, or both.

Not Enough Permissions

You don’t have the required permissions to create applications in CloudHub on the target environment.

Your user ID must be assigned the roles Design Center Developer and CloudHub administrator.

Not Enough Workers

There aren’t enough workers in the target environment.

Contact your Anypoint Platform organization’s admin about reassigning resources or acquiring more resources for designing Mule apps.

Not Ready to Run

Either your flow is not yet built enough to run, or it contains errors.

Ensure that you have a trigger for all flows and at least one card after each trigger. Also, ensure that there are no error indicators on the cards.

Operation Failed

The Mule runtime failed to process the request (while starting or stopping).

View the log for your project, which you can do by clicking Log in the bottom-left corner of the screen. There should be an error message that indicates the reason for the failure, what to do to resolve the problem, or both.

Packaging Failed

Flow Designer failed to build your Mule app package. The Flow Designer builds a package of your app as part of the process of running it.

View the log for your project, which you can do by clicking Log in the bottom-left corner of the screen. There should be an error message that indicates the reason for the failure, what to do to resolve the problem, or both.

Service unavailable

The status was retrieved by Flow Designer, the response is 503 Service Unavailable. During planned maintenance, a 503 error is to be expected for a short time.

Check status.mulesoft.com to see whether there is any planned maintenance taking place.

Undeployed

Your application is not running in CloudHub. The reason might be that your app does not have a workspace in CloudHub, the CloudHub worker has crashed, or someone has stopped the application in Runtime Manager.

Click Run if you want to redeploy your application. (Note: The Deploy button actually promotes your application to another environment. The Run button runs your application by deploying it to the Design environment.)

Unknown

The status was retrieved by Flow Designer, but the response is an unknown worker state.

Open a support case for Flow Designer. In the support case, include both the name of your project and the name of your application in CloudHub.

Workspace Creation Failed

There was an unknown error while creating the worker.

View the log for your project, which you can do by clicking Log in the bottom-left corner of the screen. There should be an error message that indicates the reason for the failure, what to do to resolve the problem, or both. You can also look in the log for Runtime Manager.