A callable recipe will auto-start when it is called synchronously but if it is call asynchronously it does not auto-start (parent recipe fails with error message, "Recipe is not started(id:XXX)". It would be great if a callable recipe could auto-start in both cases.
Thay would be very usefull and will avoid to loose quite a lot of time.
At leat in the error message to add that the REcipe should be Started if they have been called asynchronously.
Can't you put the errors in a table, and have a recipe restart recipies by using certain error codes?
We're doing something like that with a Sharepoint list
Yes, we could probably leverage RecipeOps to catch these and auto-start the called recipe and even repeat the parent. This doesn't affect us in our Production environment as we don't stop recipes there. It is more in our Dev environment where people are testing. It is more of an inconvenience than anything else. And behavior is different between sync vs async call so just a little annoying.
Send us a ticket, we will try our best to assist you with your problem