We use an on-premise instance to access adobe campaign classic V7 build 9349. Lately, we have seen almost all the workflows going to the finished state without processing. The workflow on schedule or an external signal just starts upon a trigger or on schedule and goes to the finished state. This happened when we were using build 8860, and upon suggestion from Adobe, we upgraded the build in July 2022 to use 9349, but still the issue persisted.
Can you suggest if a retry mechanism can be added to the workflows if it goes to a finished state to have it restarted automatically without manually restarting it?
We need help resolving the issue as many of the campaigns are on schedule, and the marketing communications should go as scheduled.
Note: This happens with all our workflows (Techincal workflows/Business campaigns/ Out of box workflows (Ex: Campaign Jobs, Offer Notification, etc.)
Topics help categorize Community content and increase your ability to discover relevant content.
First, can you provide a list of running services in your on-premise instance by running the following commands and send us the screenshot/dump.
Can you make sure your client version is the same as your server version, I recall an old issue with schedulers not firing correctly due to client side issue being the culprit.
Attached is the list of running services.
Also checked the client version and is same as the server version.
Do your workflows run fine if you execute them from the command line?
Can you check if there is any unwanted file lying in the root directory of the disk partition where your Adobe Campaign server is installed? If yes, then I suggest to remove it.
Let us know if this helped.
hi @isahore_old ,
Never tried from command line as the workflow server is hosted on a appserver and we are on an on premise instance.
Checked the root directory of the disk partition, there is nothing unwanted to remove.
Do you know of any other reasons that could be a possible root cause for this issue?