We're running Indigo jobs through a PowerSwitch workflow and into a hotfolder at the Indigo RIP. When the Indigo gets shut down for any length of time, the connection from PowerSwitch is stopped and released jobs get backed up and stuck until:
1. The Indigo PC is back on
2. The hotfolder is remounted on PowerSwitch's server.
3. The flow that handles the Indigo Queue is stopped and restarted.
The server is not accessible to the Indigo operator, and he is dependent on someone from prepress being there to reconnect the server to get files.
I'd like to look at this from a different direction. Can the Indigo RIP have the hotfolder located on the PowerSwitch server? (or any remote server that's always on for that matter?)
That way the Indigo RIP is retrieving files (when it's turned on) instead of waiting to receive files from a server that is unable to reconnect.
Thanks,
Mike Winker
1. The Indigo PC is back on
2. The hotfolder is remounted on PowerSwitch's server.
3. The flow that handles the Indigo Queue is stopped and restarted.
The server is not accessible to the Indigo operator, and he is dependent on someone from prepress being there to reconnect the server to get files.
I'd like to look at this from a different direction. Can the Indigo RIP have the hotfolder located on the PowerSwitch server? (or any remote server that's always on for that matter?)
That way the Indigo RIP is retrieving files (when it's turned on) instead of waiting to receive files from a server that is unable to reconnect.
Thanks,
Mike Winker
