Tim, nice to see you again :-) > Not on this specific action but I've seen other developers find some RQLs > trigger asynchronous functions. I can't recall if you'll have access to > async queue in a programmatic means but if this is one of these without > doing timeouts and retries, you'd need to interrogate that queue, find the > right process check it until done then call your next RQL. Pragmatically > timeouts and retries are easier, sure you can validate with via a support > ticket that it uses async queues for this. If you were to delete a page > linked in 50 different locations there would be more work to do so the use > of the async queue on this type of function makes sense in the product. > > We have decided to use a configurable timeout for this situation. If we run into any other problems we are going to change this but currently this is fine :-)
> PS: if you have KC access as a partner keep an eye on the API developments > with v11.1 and up > https://knowledge.opentext.com/knowledge/cs.dll/open/29560823 > > Will do :-) Best, Hilmar -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. Visit this group at http://groups.google.com/group/reddot-cms-users?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
