C4C workflows scheduled for short time in the future

[samirv]

We have a number of workflows in our production tenant that are scheduled to for a "short" time in the future - for example :

We keep getting recurring issues where the workflows rules stop working i.e. not executing at the time they should. (e.g. minutes or hours later than expected).

My questions are :

1. Does anyone else use future schedule workflow rules that are a scheduled for a short time in the future (say less than 100 seconds)
2. If so, do you also face regular issues of the workflow rule not executing when expected (e.g. minutes or hours later than expected).
3. Does anyone have any idea why they are not working - i.e. is it not recommended to use future scheduled workflow rules that are a "short" period of time in the future?
4. Are there any best practices regarding choosing a time in the future - i.e. does increasing the time increase the probability that it will be executed when expected?

Note we have already in the past reached out to SAP on these issues but we have not been able to get anything concrete so far (they recommended for example increasing the above one from 25 seconds to 1 minute in the future but we are still getting the issues), hence reaching out to others here who may be able to provide general guidance on workflow rules that are scheduled a short time in the future.

Note also that if we changed the rule to "on save" that would be a potentially different system/business process behaviour when combined with other on save workflows we have, so I am not considering that at this stage unless it proves necessary.

[prego7493]

I would try deactivating those in a lower environment for testing to see the effect. I'm sure at least one of them is the reason for this delay.

[samirv]

Hi Markus,

Thanks for the suggestion, this would be a bit tricky because :

1. we are only made aware of the issue in production tenant.
2. the issue is intermittent and happens now and again so don't know when it might happen.

[prego7493]

How many workflows do you have that trigger based on the "Changed On"?

Are there any functionalities that slow down processing of the Case object after it's being changed?

[samirv]

We have 9 workflows triggered based on "Changed on".

We have an extensive PDI solution that is triggered on save.

We also have a large amount of other workflows on save, some of which will get executed for each case, depending on the conditions.