What to do when TIBCO Data Virtualization triggers aren't firing?
                    
                
                
                    
                        book
                        
Article ID: KB0076160
                        
                    
                    
                        calendar_today
                        
Updated On: 
                    
                 
                
                
                
                    
                
                    
                        
                            
                                
                                    
                                
                                
                                
                                    
                                        | TIBCO Data Virtualization | 7.0 and higher | 
                                
                            
                         
                        
                        
                     
                    
                    
                    
                        
                            
Description
                        
                        
                            What to do when TIBCO Data Virtualization triggers aren't firing
                         
                     
                    
                    
                    
                    
                        
                            
                                
Resolution
                            
                            
                                It is possible that trigger invocation has been turned off. This may be checked as follows.
1. Open TDV Studio and connect to your TDV server.
2.  Go to Administration >> Configuration >> Server >> Configuration >> Runtime Processing Information >> Triggers
3.  Inspect the value of the Trigger Invocation Disabled setting. If the value is True, change it to False.
4. Test one of the triggers. 
5. Inspect the file <TDV_INSTALL>\logs\cs_server_events.log.  An entry of the type "START   trigger" should appear in the log, as shown below.
---------------------------
2020-01-16 08:00:00.003 -0500    INFO    START   trigger name=/shared/tests/Marketing_Trigger type=TIMER action=REINTROSPECT       1       joe        comp  20400       5216738407026   5216738407026    /shared/tests/Marketing_Trigger   TIMER   REINTROSPECT
--------------------------
The presence of this entry verifies that the trigger was executed.
 
                            
                         
                        
                    
                        
                            
                                
Issue/Introduction
                            
                            
                                What to do when TIBCO Data Virtualization triggers aren't firing?
                            
                         
                        
                    
                    
                    
                
                    
                        
                            Was this article helpful?
                        
                        
                            
                                thumb_up
                                Yes
                            
                            
                                thumb_down
                                No