Idea Details

FOKUS: JOBF don't retry in any way when a problem during transfer occurs

Last activity 04-13-2018 04:39 PM
Carsten Schmitz's profile image
04-13-2018 04:39 PM

(German summary at the end)

When an interruption during a file transfer (JOBF) happens (e.g. due to a brief network issue), the Automic OS agent will not retry the transfer at all. I propose the agent should attempt a (configurable) number of retries at an (ideally) configurable interval.

Rationale: Occasional network problems, packet loss etc. are a fact of life. Users see Automic as a professional tool, and expect the built-in file transfer to be as reliable as reasonably possible. It's not unreasonable to expect a tool to retry an interrupted transmission for a number of times. It's not reasonable to ask users to catch aborted JOBFs by means of Post Conditions or JOBP flows, since that would mean adding the logic to near each and any JOBF, just in case.

Automic has confirmed that the agent currently does not retry at all in REQ00219541.

---

JOBFs versuchen einen Dateitransfer nicht erneut, wenn er unterbrochen wird (z.B. von einer kurzen Netzwerkstörung). Diese Idee argumentiert, dass der Agent versuchen solte, den Transfer innerhalb einer sinnvollen Periode (konfigurierbar) zu Ende zu bringen. Grund: Anwender sehen Automic als ein Profi-Tool, und erwarten, dass die Engine alles tut, um einen angeforderten Dateitransfer durchzuführen. Kleine Netzwerkaussetzer und ähnliches per Post Conditions abzufangen (z.B. "wenn nicht erfolgreich dann solange Neustart, bis Erfolg)" ist nicht wirlich vermittelbar, denn dann müsste man das eigentlich in so gut wie jeden JOBF einbauen.