question Re: Retry impacts scheduler in Support Questions

Retry impacts scheduler

nisaar — Fri, 24 Apr 2026 11:01:19 GMT

Have enabled retry option in ListSMB and FetchSMB, since for some reason they are not able to list/fetch files in first attempt.

However, on retry the processor lists and fetches the file successfully.

But, the scheduler is skips fews runs.

Example:

Scheduler is set to run every 30 min and let's assume the job first runs at 00:00 AM.

On first run it fails to either list/fetch the file and the retry kicks in and the files is listed and fetched successfully.

But, the next scheduler run which is suppose to be at 00:30 AM and 01:00 AM are skipped.

Would like to know why retry is impacting scheduler.

Thanks.

Re: Retry impacts scheduler

MattWho — Fri, 24 Apr 2026 15:09:41 GMT

@nisaar

Just so I am clear in your dataflow setup...

- ListSMB processor configured to use cron scheduling (get scheduled for ru every ~30 mins)
- ListSMB "success relationship" routed via a connection to FetchSMB processor
- FetchSMB configured to use Timer Driven scheduling with:

- Flow looks like this:

The "retry" when set on a relationship controls whether a FlowFile remains on the inbound connection to the processor or gets routed immediately to the destination relationship. The number of retries is how many attempts will be made to reprocess the source FlowFile before finally routing to the destination relationship. You have 2 so that FlowFile will get terminated if it is not successfully fetched after 2 failed attempts.

I am not clear on this statement you made:

On first run it fails to either list/fetch the file and the retry kicks in and the files is listed and fetched successfully.

There is no "retry" on the listSMB. It simply get scheduled to run at the configured run schedule and listed based upon previous stored state and processor property configuration.

1. How are files being added to the source SMB directory?
2. As files are added how is the the last modified timestamp being updated? (if they are being moved to the SMB as an atomic move, the timestamp on the file may not change which can result in ignored files because another file already listed resulted in sate holding a more recent timestamp).
3. What "Listing strategy" are you using? I recommend using "Tracking Entities" to avoid issue from question 2 above.

Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped.

Thank you,
Matt

Re: Retry impacts scheduler

nisaar — Mon, 27 Apr 2026 09:37:22 GMT

@MattWho

Thanks for your reply.

Flow setup

Its s 4 node Cluster.

ListSMB details

Listing Strategy : No Tracking

FetchSMB Details

Assume the first run starts at 12:30 AM. It usually fails either during ListSMB or FetchSMB with the error shown below.

The retry then starts at 12:32 AM, and that run completes successfully. It is able to list the files and fetch the file from the SMB location without any issue.

However, the next scheduled run at 1:00 AM gets skipped, and at times even the 1:30 AM run is skipped as well.

After one or two skipped runs, the scheduler starts again, but the same pattern repeats: the first attempt fails, the retry succeeds, and then a few subsequent scheduled runs are skipped.

I would like to understand whether enabling retry has any impact on the scheduler behavior.

Note: We are able to connect to SMB using MacOS finder and also from Java Code where we can list and fetch the file without any issue.

Thanks

Re: Retry impacts scheduler

MattWho — Mon, 27 Apr 2026 13:54:17 GMT

@nisaar

I see you set retry on the ListSMB processor "success" relationship. You should never set retry on any "Success" relationship. The connection retry logic is triggered when a FlowFile would be routed to the relationship. Instead of routing the FlowFile to the relationship it remains on the upstream connection to be "retried". That means that only when FetchSMB successfully lists a file will it trigger retry. Plus retry implies a there is some upstream location to persist a source FlowFile. Only once all retry attempts are exhausted will the FlowFile actually be placed on the connection containing the "success" relationship. I would expect unexpected behavior with such a configuration.

Using "retry" on a failure or other error type relationship makes sense since these are the relationships you don't expect FlowFiles to be routed to. so makes sense on your FetchSMB processor so that source FlowFile will remain on the inbound connection to FetchSMB until both the configured retry attempts are made. I both retries fail I see you terminate the "Failure" relationship which effectively throws away that file. I don't know that terminate is what i would do here either since ListSMB was successful in order to produce FlowFile waiting at FetchSMB. Plus state is recorded by ListSMB and the file that failed ot be fetched would never get listed again unless you touched file to update last modified time or cleared state on listSMB processor.

Thank you,
Matt

Re: Retry impacts scheduler

nisaar — Mon, 27 Apr 2026 18:49:03 GMT

@MattWho

Have remove the retry on ListSMB.

Now, when I do "Run Once" on ListSMB for first time I get below error

ListSmb[id=678b3091-1e8c-38c6-a274-0d2eb00c91cb] Failed to perform listing on remote host due to Could not perform listing: java.io.IOException: Could not perform listing
- Caused by: java.io.IOException: Could not create session for share smb://ifiler-smb03:445/SFTP
- Caused by: com.hierynomus.smbj.common.SMBRuntimeException: com.hierynomus.protocol.transport.TransportException: java.util.concurrent.ExecutionException: com.hierynomus.smbj.common.SMBRuntimeException: java.util.concurrent.TimeoutException: Timeout expired
- Caused by: com.hierynomus.protocol.transport.TransportException: java.util.concurrent.ExecutionException: com.hierynomus.smbj.common.SMBRuntimeException: java.util.concurrent.TimeoutException: Timeout expired
- Caused by: java.util.concurrent.ExecutionException: com.hierynomus.smbj.common.SMBRuntimeException: java.util.concurrent.TimeoutException: Timeout expired
- Caused by: com.hierynomus.smbj.common.SMBRuntimeException: java.util.concurrent.TimeoutException: Timeout expired
- Caused by: java.util.concurrent.TimeoutException: Timeout expired

when I do "Run Once" second time on ListSMB, Its able to list the file.

But, FetchSMB fails to fetch few files with below 2 type of errors.

Not all files fails though.

FetchSmb[id=6b1f9f93-4d76-38fc-94ed-08918722a36b] Could not fetch file OTL-Prod-Reports/OTL_Manual_Override//Errors_and_Warnings/Events/Events_OTL_Override_Error_Warnings_2026_04_24.csv.: java.io.IOException: Could not create session for share smb://ifiler-smb03:445/SFTP
- Caused by: com.hierynomus.smbj.common.SMBRuntimeException: com.hierynomus.protocol.transport.TransportException: java.util.concurrent.ExecutionException: com.hierynomus.smbj.common.SMBRuntimeException: java.util.concurrent.TimeoutException: Timeout expired
- Caused by: com.hierynomus.protocol.transport.TransportException: java.util.concurrent.ExecutionException: com.hierynomus.smbj.common.SMBRuntimeException: java.util.concurrent.TimeoutException: Timeout expired
- Caused by: java.util.concurrent.ExecutionException: com.hierynomus.smbj.common.SMBRuntimeException: java.util.concurrent.TimeoutException: Timeout expired
- Caused by: com.hierynomus.smbj.common.SMBRuntimeException: java.util.concurrent.TimeoutException: Timeout expired
- Caused by: java.util.concurrent.TimeoutException: Timeout expired

FetchSmb[id=6b1f9f93-4d76-38fc-94ed-08918722a36b] Could not fetch file OTL-Prod-Reports/OTL_Manual_Override//Errors_and_Warnings/New_Stores/NewStores_OTL_Override_Error_Warnings_2026_04_25.csv.: java.io.IOException: Could not create session for share smb://ifiler-smb03:445/SFTP
- Caused by: com.hierynomus.smbj.common.SMBRuntimeException: com.hierynomus.protocol.transport.TransportException: Cannot write SMB2_SESSION_SETUP with message id << 169 >> as transport is disconnected
- Caused by: com.hierynomus.protocol.transport.TransportException: Cannot write SMB2_SESSION_SETUP with message id << 169 >> as transport is disconnected

Thanks

Re: Retry impacts scheduler

nisaar — Mon, 27 Apr 2026 19:12:58 GMT

@MattWho

Have removed retry from ListSMB,

Now, when I run ListSMB for first time using "RunOnce" I get below error.

On running ListSMB second time using "Run Once" Its able to list the file.

But FetchSMB fails to get the file with 2 types of errors.

Not all files fails though. There is no issue with the file, since files fail randomly.

Re: Retry impacts scheduler

nisaar — Mon, 27 Apr 2026 19:16:08 GMT

Have removed the Retry on ListSMB