This article provides the steps necessary to prevent a File, Query, or Timed integration running in the Default or a Custom based Processor Group from being sent to the ScribeRetry message queue.

Starting with 7.9.x File, Query, or Timed integrations, which normally run in the Serial processor group, can now be run in the Default or a Custom based Processor Group.
These jobs are treated the same as a Queue based integration in that when the job fails it is sent to the ScribeRetry message queue for reprocessing.
In many cases this is not the desired behavior.

Unlike the Queue based integrations, the File, Query, or Timed integrations do not have an On Retry tab for setting the number of retries. 
A default value of 120 is used and any value greater than zero causes a failed job to go into the ScribeRetry queue.

To prevent a File, Query, or Timed integration from going into ScribeRetry queue, the number of retries must be set to zero in the ScribeInternal database.
This can be set on an integration by integration basis. 

The query below sets the number of retries to zero for ALL File, Query, or Timed integrations utilizing the Default or a Custom based Processor Group.
The TIBCO Scribe® Insight services must be restarted after running the query.
 

Update Scribe.QueueEvents Set RETRYCOUNT = 0 
Where ListenerId In 
  (Select ListenerID From Scribe.Listeners (nolock) Where EventType <> 'Queue' AND MessagePool <> 'Serial')