SDR Replication Setting - Replication Status "Executing" should be added

The SDR “Replication Status” column in Replication Monitor should update to a new value, “Executing” as soon as the replication begins to query the system. Currently the status does not appear to update to “Refreshing” until data is being pulled from the system leaving the possibility of a replication running the extraction query against the system connection without the user being aware that it is running. This way when a query is executing against the system with a complicated filter that could timeout you are aware that it is processing against the system and can disable it if it is running long.

This lack of clarity in status plus the default design of SDR to retry the replication indefinitely has caused a long running filtered replication to nearly crash a production system using up extensive resources without any awareness that it was still running.

The last replication status showing as “Error” after the first time out, but the job continuing to run, exacerbated the issue making it look like it had errored out.