Alex, No, a Processor’s state is read-only from the user point of view, and the state is tied to the identifier of the Processor. It’s not possible to transfer state from one Processor to another.
Thanks -Mark > On Mar 22, 2021, at 11:01 AM, Oleksandr Bondarenko <ob...@ciklum.com.INVALID> > wrote: > > Hello! > > Are there any possibility to start newly created ListAzureDataLakeStorage > processor from some specific state which was reached by a previously > deleted ListAzureDataLakeStorage? And, in general, is it possible to > transfer state between processors of the same type? > > Regards, > > Alex > > -- > > Ciklum refers to one or more of Ciklum Group LTD. and its subsidiaries and > affiliates each of which is a legally separate entity. Ciklum LLC is a > limited liability company registered in Ukraine under EDRPOU code 31902643, > with its registered address at 12 Amosova St., 03038, Kyiv, Ukraine. > > > > The > contents of this e-mail (including any attachments) are confidential and > may be legally privileged. If you are not the intended recipient of this > e-mail, please notify the sender immediately and then delete it (including > any attachments) from all your systems. Any unauthorised use, reproduction, > distribution, disclosure and/or modification of this message and/or its > contents are strictly prohibited. We cannot guarantee that this e-mail is > secure or error-free. Ciklum cannot be held liable for any loss or damage > caused by software viruses or resulting from any use of or reliance on this > email by anyone, other than the intended addressee to the extent agreed in > a contract for the matter to which this email relates (if any). Messages > sent to and from Ciklum may be monitored; by replying to this e-mail you > give your consent to such monitoring. Notice: we do not accept service by > e-mail of court proceedings, other processes or formal notices of any kind > without specific prior written agreement. This email does not constitute a > binding offer or acceptance for Ciklum unless so set forth in a separate > document. > >