Within BPML, SFTPClient operation set needs a way to check status of an active session: introduce SFTPClientSessionStatus call.

One fundamental problem is that sometimes the SFTP Session will inadvertently end mid-operation, perhaps closed by server. When this happens, an operation call like SFTPClientList or SFTPClientPut will simply fault. It will return a SessionEndTime, but this is the only way to know the session has died. When this happens, the SessionToken is still in ProcessData, but a call to SFTPClientEndSession will fault because the SessionToken is no longer valid.

One possibility is the SFTPClientEndSession never faults. If the token is no good, it simply returns the current status and does nothing.

But having a status check call can be useful.

A call to SFTPClientSessionStatus will return the current session status and state, as implied.

Ideally, it should be possible to call this function periodically while another operation is in progress, as it doesn't really communicate with the server, but just the status of the client session itself.

Suppose <all> is used to parallel two separate sequences: one is used to actually call an SFTPClientPut or SFTPClientGet operation. The second parallel sequence can periodically call SFTPClientSessionStatus, say every minute with a sleep in between. This will show that the the file transfer is in progress, along with its current progress. This allows an opportunity to update a db table with its progress, or be aware that something has gone wrong.