I have created a schedule in RC for a load process that runs about 10-15 minutes. When I did this in our development environment, at the point I selected the fex for the schedule, it appeared RC would hang every time I did this. I thought it was something in the fex causing this, so I commented out most of the fex and then was able to add the report fex to the schedule. Once it was added, I then re-enabled the code.

Now I am working with a client to implement this new schedule in production, and we are having the same issue with the load fex. When we selected the fex for a new schedule, we checked the reporting server console to see if anything was going on there. To my surprise, the load fex was running! Apparently, when you select a fex when creating a schedule, it runs the fex for some reason. So, we just waited out the fex, and once it was complete, we were able to save the schedule.

My question is - is there any way to keep RC from running the fex when you select it for a new schedule? This doesn't make any sense to me, and I just want to know if there is a way to turn this off. Does anyone know why it is doing this, and how to keep it from running the fex?

This message has been edited. Last edited by: Kerry,

raise a case with IBI.
It should definately not be doing that.
It has an irritating feature that it runs the task when you save it.
However it should not run when you are selecting it.

I am planning on opening a case with IBI, but wanted to check the Focal Point community first.

Thanks!