The default behaviour via eclwatch sprays and fileservice sprays is to perform no replication and to publish the file with no redundancy.
In older builds (e.g. 5.6.8), although the UI and fileservice defaults have not changed, files were published with redundancy on.
That in effect meant replicate later/asynchronously (via backupnode).
We should ensure that default behaviour is reinstated. At a later time we can give users the option of spraying without any redundancy, with immediate redundancy or with delayed/async redundancy (See HPCC-19439).
The UI spray interface should be changed to reflect that delayed replication is the default.