I do not see any errors in logs while renaming the job. but i see some errors while i try to load the project with several jobs.the concern is mostly on the errors while renaming the project.

Hi @Tethich i couldn't find any specific errors in logs as such. but tried to narrow down the OOTB file which is responsible for the issue /libs/clientlibs/granite/coralui3/js/all.jsNot sure how to proceed further can i raise AMS ticket? 

Hi All, I am trying to create a translation job where the job gets created successfully but on trying to rename the job it usually keeps loading with 500 server error pointing to issue with granite.min.js. Also noticed console errors like  DuplicateDefinitionError as below in coralUi3 when project i...

@giuseppebag Thanks for the info. i tried creating page under same path in author and published date No error in logs. page was visible card carousel componentAlso created page and then package of it w/o publishing page installed the package in publisher -- Nor errors in logs. page wasn't visible.ch...

@giuseppebag Got it but why only for one page. Apologies for clinging on to same question. i feel even though it had filters shouldn't it be applicable for entire node instead of just one page.

@giuseppebag Thanks for the detailed list. How do i check for custom replication filters or preprocessors in publishers?Also this is just happening with only one page in the card carousel component but rest are fine? 

Not yet, will keep it posted as i venture right answer further help would benefit 

Hi @ManviSharma Yes the originalPublishedDate is explicit for the page to be visible i tried removing the date in existing pages of card Carousel the page will simply not be visible. i created page in local author and tried to reproduce same scenario in local publisher via package. And the page was ...

Hi @aanchal-sikka i tried to check the config suggested. the values appear to be same in both the publishers.only type=jcrvlt is jcr packages and dot missing in package filters rep:cache valuei did not observe 

@aanchal-sikka I am not sure if it is OOTB Replication properties being used? or Are we selecting pages based on OOTB replication date? but pages can be enabled and disabled either from actual published date or from the republished date. yet to check this. But whatever the case is shouldn't it work ...