[SOLVED] Unable to change status when script has an error

@Sebastian a critical bug in production has hit us suddenly since last 2 days. We are unable to publish content in articles schema of both vannatest(production app) and vannadevd(development app)

I have…

  • [] Checked the logs and have uploaded a log file and provided a link because I found something suspicious there. Please do not post the log file in the topic because very often something important is missing.

I’m submitting a…

  • [ ] Regression (a behavior that stopped working in a new release)
  • [x] Bug report
  • [ ] Performance issue
  • [ ] Documentation issue or request

Current behavior

  1. Unable to publish an article after saving the status change from Draft to Ready to Approved
  2. Error I am getting in history logs is as follows

failed to schedule status change for article

Expected behavior

Should be able to publish the article

Minimal reproduction of the problem

App: vannatest in Cloud
Create a new article with minimum fields required and try to publish it


  • [ ] Self hosted with docker
  • [ ] Self hosted with IIS
  • [ ] Self hosted with other version
  • [x] Cloud version

Version: [VERSION]


  • [x] Chrome (desktop)
  • [ ] Chrome (Android)
  • [ ] Chrome (iOS)
  • [ ] Firefox
  • [ ] Safari (desktop)
  • [ ] Safari (iOS)
  • [ ] IE
  • [ ] Edge


The status field should not matter. Do you use scheduled publishing?

@Sebastian I have cross checked with the publishing team and received a confirmation, WE HAVEN’T USED scheduled publishing. The error is coming in both the apps vannadevd and vannatest so I am assuming we haven’t made any change and it’s probably a new deployment at Squidex level.

Thank you. I have just downloaded the full backup of the production system and as soon as I have it running I will have a look.

Hi, the problem is your script, but it could be made it a better way.

@Sebastian Please can you help me…exactly how I can fix the Script in which part?

You cannot use replace in the change event, only in update and create.

1 Like

@Sebastian Thanks, that fixed the problem. Great Thank you for relief.

But it is a bug that the real exception has been swallowed. I am bout to fix that.

1 Like