Can anybody tell me what the problem is when i get this
"no outgoing connection accepts this job"
no outgoing connection
-
dkelly
- TOP CONTRIBUTOR
- Posts: 658
- Joined: Mon Nov 29, 2010 8:45 pm
- Location: Alpharetta GA USA
- Contact:
no outgoing connection
The most common cause of this error is having a flow connection that has only 'include files' option set. If say a TIFF is processed and the 'include files' is configured to only allow PDF files, then that error will be raised.
If you add a second flow connection with neither include or exclude files set OR has include set to the opposite of other flow connection then the error won't happen.
Example 1:
---> + include .tiff ---> output #1
|
+ exclude .tiff ---> output #2
Example 2:
---> + include .tiff ---> output #1
|
+---> output #2
Dwight Kelly
Apago, Inc.
dkelly@apago.com
If you add a second flow connection with neither include or exclude files set OR has include set to the opposite of other flow connection then the error won't happen.
Example 1:
---> + include .tiff ---> output #1
|
+ exclude .tiff ---> output #2
Example 2:
---> + include .tiff ---> output #1
|
+---> output #2
Dwight Kelly
Apago, Inc.
dkelly@apago.com
no outgoing connection
Let me add some words to Dwight's explanation:
Example 1 will actually work, but is advised against as a general principle. Using an include / exclude pair works, but is harder to maintain. In general it is better to use a connection that uses include filters and have a connection that uses the "All other files" filter. In that way maintenance is easier - if you add other "include" connections later, your construction will just continue to work.
So:
---> + include .tiff ---> output #1
|
+ All other files ---> output #2
Example 2 will work as well, but might not do what is intended. As the second connection has no filters at all, all files will be copied to the second connection as well. If you want TIFF files to be filtered out to output 1 and all other files to go to output 2, this construction won't do that.
dkelly wrote: The most common cause of this error is having a flow connection that has only 'include files' option set. If say a TIFF is processed and the 'include files' is configured to only allow PDF files, then that error will be raised.
If you add a second flow connection with neither include or exclude files set OR has include set to the opposite of other flow connection then the error won't happen.
Example 1:
---> + include .tiff ---> output #1
|
+ exclude .tiff ---> output #2
Example 2:
---> + include .tiff ---> output #1
|
+---> output #2
Dwight Kelly
Apago, Inc.
dkelly@apago.com
Example 1 will actually work, but is advised against as a general principle. Using an include / exclude pair works, but is harder to maintain. In general it is better to use a connection that uses include filters and have a connection that uses the "All other files" filter. In that way maintenance is easier - if you add other "include" connections later, your construction will just continue to work.
So:
---> + include .tiff ---> output #1
|
+ All other files ---> output #2
Example 2 will work as well, but might not do what is intended. As the second connection has no filters at all, all files will be copied to the second connection as well. If you want TIFF files to be filtered out to output 1 and all other files to go to output 2, this construction won't do that.
dkelly wrote: The most common cause of this error is having a flow connection that has only 'include files' option set. If say a TIFF is processed and the 'include files' is configured to only allow PDF files, then that error will be raised.
If you add a second flow connection with neither include or exclude files set OR has include set to the opposite of other flow connection then the error won't happen.
Example 1:
---> + include .tiff ---> output #1
|
+ exclude .tiff ---> output #2
Example 2:
---> + include .tiff ---> output #1
|
+---> output #2
Dwight Kelly
Apago, Inc.
dkelly@apago.com