Error Handling Deployments

Access denied

Your account does not have permission to perform this action.

Ask your administrator for the required permission.

No connection, check your internet connection and try again

The Control Hub could not reach the platform.

Check your connection, then reload the page or apply your change again.

Service temporarily unavailable, try again later

The platform service performing this action is temporarily unavailable.

Wait a moment, then reload the page.

Unexpected error, try again

An unexpected server error occurred.

Try the action again. If the problem continues, contact your administrator.

Changes could not be saved, try again

The platform could not store the configuration.

Apply the change again. Your edits are kept, so nothing is lost. If the problem continues, contact your administrator.

Configuring a Deployment

Conflict detected, reload and try again

Another update changed the deployment while you were editing its configuration.

Copy your text, reload the page, then apply your change again.

Configuring a Deployment

Content not found, may have been removed

The deployment or the component no longer exists.

Return to the Deployments view and reload it.

Working With the Deployments View

Fields contain invalid or missing values

The configuration is valid JSON, but the platform rejected values it contains.

Correct the reported values and apply again. Compare your values with the Initial configuration to see which values the deployment expects.

Configuring a Deployment

Invalid JSON

The text in the Custom Changes panel cannot be read as JSON.

Correct the text. Apply becomes available again as soon as the text is valid. Use Discard to return to the values last stored.

Configuring a Deployment

Invalid request, check your input and try again

The configuration does not match the structure the platform expects. Text that is valid JSON is not necessarily a valid configuration.

Compare your values with the Initial configuration, correct the structure, and apply again.

Configuring a Deployment

Loading took too long, try again

The configuration could not be loaded within the expected time.

Reload the page. If the problem continues, contact your administrator.

Service temporarily unavailable, try again later

The platform service that holds the configuration is temporarily unavailable.

Wait a moment, then reload the page.

Both editors are empty and read-only, and a message is shown below the text.

The configuration could not be loaded. All three parts are loaded together, so one failure concerns all of them.

Resolve the problem the message reports, then reload the page. Nothing can be edited until the configuration loads.

Configuring a Deployment

The Apply button is not offered.

There are no unsaved changes, the text is not valid JSON, or an apply is still running.

Check the status below the text. If it reports Invalid JSON, correct the text. If the button reads Applying …, wait until the apply has finished.

Configuring a Deployment

The format action is not offered.

The text is already formatted, or it is not valid JSON.

Correct the text if it is invalid. Otherwise there is nothing to format.

Configuring a Deployment

Discard and Apply are not available and the text cannot be edited.

An apply is in progress. The values the platform reports back replace what you sent, so an edit made in between would be lost.

Wait until the apply has finished. Both actions are available again afterwards, whatever the outcome.

Configuring a Deployment

The Open Logs action is not displayed.

The PAS Resource Monitor is not configured for your installation, or the deployment has no components.

Ask your administrator to configure the PAS Resource Monitor.

Inspecting Logs

No deployments yet. Go to the Catalog to deploy your first project.

Nothing is deployed yet, or no deployment matches the current search and filters.

Clear the search and the filters. If nothing is deployed yet, select the Catalog link to deploy a project.

Deploying a Project

A deployment or a component you expect is missing from the list.

A search term or a filter is active, or the deployment is listed on another page.

Clear the search and the filters, then move through the pages of the list.

Working With the Control Hub

The Deployments view shows an error message with a recovery action.

The list of deployments could not be loaded.

Select the recovery action to load the view again. If the problem continues, contact your administrator.

Working With the Deployments View

Conflict detected, reload and try again

Another update changed the deployment.

Reload the Deployments view, then try the action again.

Working With the Deployments View

Deletion not possible, try again

The delete request did not complete.

Try the deletion again. If the problem continues, contact your administrator.

Deleting a Deployment

A notification states an error message and offers Retry and Copy error message.

The Control Hub did not accept the update request. The message states the reason.

Click Retry to send the same request again. Click Copy error message to copy the cause, for example for your administrator or for a support request.

Updating a Deployment

Conflict detected, reload and try again

Another update changed the deployment in the meantime.

Close the dialog and reload the Deployments view. Check which version the deployment runs, then update again if needed.

Updating a Deployment

Content not found, may have been removed

The deployment or the selected project version no longer exists, for example because another user deleted it.

Reload the Deployments view. If the deployment still exists, open the update dialog again and select an available version.

Updating a Deployment

<deployment name> could not be updated to <version>

The Control Hub accepted the update, but the deployment does not run on the new version. The status of the deployment is failed or degraded, for example because a component does not start.

Open the deployment details page and check the status of the components. Open the logs of the component that does not run. Click Copy error message in the notification to copy the cause. Do not repeat the update to the same version. Update the deployment to another version.

Invalid request, check your input and try again or Fields contain invalid or missing values

The platform rejected the update request for the selected version.

Select another version and update again. If the problem continues, contact your administrator.

Updating a Deployment

Request timed out or Loading took too long, try again

The platform did not answer in time.

Reload the Deployments view and check which version the deployment runs before you update again.

Working With the Deployments View

The deployment details page does not show Update.

The deployment was not made from a project version. The Control Hub cannot determine the versions that the deployment can be moved to.

Deploy the project version that you want to run as a new deployment in the Projects view.

Deploying a Project

The Update action is disabled. The message when hovering over it is: A component is not updated or deleted on its own. Act on the whole project deployment. 

You selected a component deployment. A component deployment cannot be updated on its own.

Open the More actions menu in the row of the project deployment and select Update.

Updating a Deployment

The Update action is disabled. The message when hovering over it is: You don't have the right permissions to perform this action.

You do not have the permission to change deployments on the platform that the deployment runs on.

Ask your administrator for the required permission.

Updating a Deployment

The update dialog shows an error message, and Update & Restart is disabled.

The Control Hub could not load the versions of the project. The message states the reason, for example Loading took too long, try again or Content not found, may have been removed.

Close the dialog and open it again. If the problem continues, contact your administrator.

Updating a Deployment

The version selector states No branch builds yet or No tagged builds yet.

The selected list, Branch or Tag, holds no version of the project.

Use the Branch and Tag switch to open the other list. The selector states how many versions the other list holds. If it states No build available, the project has no version that you can select.

Updating a Deployment

This version is already running. is displayed in the update dialog. Update & Restart is disabled.

The target version is the version that the deployment already runs, for example because no newer version exists.

Select another target version in the version selector.

Updating a Deployment