Unsure if this is an issue with Deploy, Replication or Relaxed. Posting here for now as it's related to deployments.

I made a deployment between 2 new lightning distribution based sites (lets call them CMS1 and CMS2). CMS1 reported a successful deployment but on CMS2 there was an error which prevented the content from being created. Once the error on CMS2 was resolved I tried running the same deployment again from CMS1 but the content did not get created. A brand new deployment did not push the content either. I assume since it was a "successful" deployment the first time around as far as CMS1 is concerned that the content got flagged as "deployed" so it's not getting redeployed.

What's the proposed resolution for such an error? Recreate the content? Create a new revision of the content? What if it happens on things like menu items or user entities which are not revisionable?

Should there be a mechanism in place to mark the content as not deployed or the deployment itself as a failed deployment if such a thing happens?

Thanks.

Comments

pavlosdan created an issue. See original summary.

jeqq’s picture

jeqq commented
Status: Active » Postponed (maintainer needs more info)

@pavlosdan Could you provide more info about the modules versions you used? Do you have any errors in logs? Creating a new revision for non-deployed content in this case could help, but it depends by the cause of the problem.

Regarding menu items - they are revisionable, non-revisionable entities are not deployable.

pavlosdan’s picture

pavlosdan
he/him/his
Primary language Greek
Location Vancouver
commented

@jeqq I was using the recommended releases of the modules at the time (betas). The only error that was logged was on the remote CMS and it was related to the translation fields that were not enabled on the remote but were enabled on the local CMS.

Didn't know menu items were revisionable! Need to look into this!

abu-zakham’s picture

abu-zakham commented
Status: Postponed (maintainer needs more info) » Needs work
blgarg’s picture

blgarg commented

Hi team,

I am also facing same issue. To make it workable, we have to restore the database from prod to stag. Again it starts working. Any Fix for this ?

Thanks,
Bhart Garg