For a deeper look into our Elektron API, look into:
Overview | Quickstart | Documentation | Downloads | Tutorials | Articles
Hi,
Thank you for your participation in the forum.
Is the reply below satisfactory in answering your question?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Hello @shehroz.khan
Thank you for your participation in the forum. Is the reply below satisfactory in resolving your query?
If so please can you click the 'Accept' text next to the appropriate reply. This will guide all community members who have a similar question.
Thanks,
AHS
Hi,
Thank you for your participation in the forum.
Is the reply below satisfactory in answering your question?
If yes please click the 'Accept' text next to the most appropriate reply. This will guide all community members who have a similar question.
Otherwise please post again offering further insight into your question.
Thanks,
AHS
Please be informed that a reply has been verified as correct in answering the question, and has been marked as such.
Thanks,
AHS
Hello @shehroz.khan,
If this error is not persistent, if it happens sometimes, it looks like a resource that RFA app needs, for example connectivity to EZD, DLL access, sufficient CPU or memory, becomes briefly unavailable to the app.
Once the availability of the resource is restored, RFA app will proceed as expected.
Does this happen at predictable times? If this is the case you may be able to figure out what causes the resource lock. I.e. market peak, or machine load peak due to other heavy jobs being run.
The other possible way to find out more is to enable tracing on RFA via trace parameters as described in RFA Configuration Guide or this thread and reviewing trace for when the issue occurs.
Hello @shehroz.khan,
Could you please give us an update:
Where you able to enable RFA tracing? Any findings?
Thanks