I Cant Deploy the cloud nvironment

0
Hi,When I try to deploy to a test or prod environment, a problem occurs during the backup phase. I receive an error, and the deployment goes into IDLE status. I have to manually start or restart the application. When I do this, it briefly shows the desired package as if it's deployed, but after a few seconds, it reverts to the package status before the deployment. The error I'm getting is related to not being able to find the schedule event microflows, even though these microflows are still present in the code. The error message:2026-03-26T14:20:21.661415 [runtime-container/77vxl] ERROR - MicroflowEngine: Microflow 'BPM.SCE_Purchase_RequestLines_Update1' could not be found2026-03-26T14:20:21.664655 [runtime-container/77vxl] ERROR - MicroflowEngine: Microflow 'BPM.SCE_Purchase_RequestLines_Update2' could not be found2026-03-26T14:20:21.666832 [runtime-container/77vxl] ERROR - MicroflowEngine: Microflow 'BPM.SCE_AdvancePayment_RequestHeader_Update' could not be found
asked
2 answers
0

Perhaps a module was renamed or microflows were renamed and the Scheduled Events are out of date. If it is only these 3 scheduled events, try deleting those scheduled events in Studio Pro, recreating them in Studio Pro and then redeploying. This would take a few minutes and would eliminate an issue with broken or out of date scheduled events.

answered
0

Hi Ayberk,


I looked into this a bit more and wanted to share the latest steps I would recommend.


If the scheduled event is still there but the runtime says the microflow cannot be found, it usually means the deployment is using an outdated or broken reference, not that the scheduled event is actually missing in Studio Pro.


This often happens after renaming/deleting microflows, module refactoring, or merges. The scheduled event may still exist, but internally it can still point to an old microflow reference.


First, I would try the safer fix:

  • reselect the microflow in the scheduled event,
  • or delete and recreate the scheduled event,
  • then create a fresh deployment package and redeploy after fully stopping the environment.


If that still does not work, then as a stronger reset:

  • delete the affected scheduled events and related microflows,
  • deploy once without them,
  • then recreate them immediately and deploy again.


That approach can help clear broken references that are still being carried in the deployment metadata/runtime state.


So this is usually not about the microflow “not existing”, but about the environment still holding an outdated reference.


After the trials, please share your update.


If this resolves your issue, you can mark it as accepted.


answered