Skip to content
← Turn your feedback into functionality

Settings and activity

2 results found

  1. API for DXP environment restart

    3 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Gathering Feedback  ·  1 comment  ·  CMS SaaS (Content Management System) » DXP, Hosting & Infrastructure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Rickard Nilsson commented  · 

    We need this too. Our production site runs on two instances and is deployed from Azure DevOps through the Deployment API with a slot swap. When a release adds new block or page types, an instance often appears to keep a content type ID in memory that has no matching row in tblContentType. Editors then cannot create content of the new type, and saving fails with a SqlException on FK_tblContent_tblContentType. Restarting the instances fixes it.

    Today that restart is a manual step in the DXP portal after most releases that add content types. An API operation that restarts the web app one instance at a time, with a status we can poll, would let us run it as the last step of the release pipeline without downtime. A matching cmdlet in EpiCloud would make it easy to use from a pipeline.

    Rickard Nilsson supported this idea  · 

  2. rolling restart flag

    2 votes

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close

    We’ll send you updates on this idea

    Gathering Feedback  ·  1 comment  ·  CMS PaaS (Content Management System) » DXP, Hosting & Infrastructure  ·  Admin →
    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback
    Signed in as (Sign out)
    Close
    Close
    An error occurred while saving the comment
    Rickard Nilsson commented  · 

    We need this too. Our production site runs on two instances and is deployed from Azure DevOps through the Deployment API with a slot swap. When a release adds new block or page types, an instance often appears to keep a content type ID in memory that has no matching row in tblContentType. Editors then cannot create content of the new type, and saving fails with a SqlException on FK_tblContent_tblContentType. Restarting the instances fixes it.

    Today that restart is a manual step in the DXP portal after most releases that add content types. An API operation that restarts the web app one instance at a time, with a status we can poll, would let us run it as the last step of the release pipeline without downtime. A matching cmdlet in EpiCloud would make it easy to use from a pipeline.

    Rickard Nilsson supported this idea  ·