We have a table which is guarded on deployment and on execution. When we run a manual execute on this table we get the message that this table is guarded, therefore not executed. This table is in a nightly execution and we don't expect this table will be executed because of the guard on execution. But we are dumbfounded that during the nightrun it is executed (and runs in an error). What are we doing wrong?
Solved
Table is guarded on execution and deployment but still executed in an execution
Best answer by RLB
The scheduler executes the latest, deployed version of the project. Guarding a table and saving the project is not enough.
Take a look at the versions of your project and check if the newest version has indeed been deployed.
So, deploy your project.
RLB: that's strange, because this table is guarded on deployment. Does guarding a table a full deployment of the entire project? We have also seen in de repo that the table is guarded. When starting the execution or deployment of this table manually we get the 'some tasks were guarded' message and no execution is started.
The scheduler executes the latest, deployed version of the project. Guarding a table and saving the project is not enough.
Take a look at the versions of your project and check if the newest version has indeed been deployed.
So, deploy your project.
+3Hi,
An option could be to use “Save project as deployed version” or "Save instance as deployed version”. Depending on which version of TimeXtender you use.
1 person likes this
Reply
Most helpful members this week
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
