Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Interpreting different publish statuses

Updated on July 14, 2022

App Studio provides various status updates throughout the publish cycle to inform you of various challenges or roadblocks your pipeline might encounter. These guardrails are intended to mitigate and resolve issues before publish failures.

See below for a few examples of the App Studio publish guardrails:

  • App Studio can only publish if there is one configured deployment pipeline in Deployment Manager. App Studio returns an error if you attempt to publish with more than one deployment pipeline configured.

  • If you have no pipelines configured, App Studio returns the following error. To add a pipeline in Deployment Manager, see Creating pipelines.
    App Studio returns an error if you attempt to publish with no deployment pipelines configured.

  • It is not recommended to have a manual transition configured in your deployment pipeline. If a manual transition is required, you can configure this at the stage level. Once the stage encounters the manual transition (after all tasks complete in the stage), the Action Required alert is displayed on App Studio. You must switch to Deployment Manager to manually promote to the next stage.
    Manual transitions are not recommended when using App Studio publish.
    • If there is any manual input or approval needed between tasks for the deployment to proceed, you can configure the Perform manual step task in the pipeline. If the deployment is waiting at Perform manual step, you can approve directly from App Studio through the Perform manual step link.
    • Use the Perform manual step action to proceed with a publish.

  • If a publish is paused, the pipeline will reflect that status with a Publish paused warning on in the stage on which it paused. To resume publication from the paused state, contact your application administrator.
    A paused publish will remain in the paused state until it is resumed.

  • If a task fails for any reason in the publish cycle, the application publish will stop. The pipeline model provides a error for the stage on which Publish failed, along with the list of failed tasks to remedy before attempting to publish your application again. Once the issue is resolved, contact your application administrator to access Deployment Manager and retry the failed task and resume publishing.
    If a publish fails due to an error with a task, App Studio provides more information on the cause of the failure by clicking the More option on the error within the stage.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us