[source-sftp-bulk] SFTP Bulk Connector Cannot find Stream

[ykursav]

Connector Name

sftp-bulk

Connector Version

1.9.0

What step the error happened?

Configuring a new connector

Relevant information

Hi All,

During configuration of connector getting error like below. Not sure really what is wrong, I tested many options with globs settings, folder path everything still keep getting this error.

Anybody encountered this error before? I tested SFTP connector, I could be able to get connection and streams but it does not have enough capabilities for my data ingestion pipeline.

Thank you all.

Relevant log output

Configuration check failed
Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/file_based/availability_strategy/default_file_based_availability_strategy.py", line 100, in _check_list_files file = next(iter(stream.get_files())) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ StopIteration During handling of the above exception, another exception occurred: Traceback (most recent call last): File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/file_based/availability_strategy/default_file_based_availability_strategy.py", line 79, in check_availability_and_parsability file = self._check_list_files(stream) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/usr/local/lib/python3.11/site-packages/airbyte_cdk/sources/file_based/availability_strategy/default_file_based_availability_strategy.py", line 102, in _check_list_files raise CheckAvailabilityError(FileBasedSourceError.EMPTY_STREAM, stream=stream.name) airbyte_cdk.sources.file_based.exceptions.CheckAvailabilityError: No files were identified in the stream. This may be because there are no files in the specified container, or because your glob patterns did not match any files. Please verify that your source contains files last modified after the start_date and that your glob patterns are not overly strict. Contact Support if you need assistance. stream=

Contribute

• Yes, I want to contribute

---

Internal Tracking: https://github.com/airbytehq/oncall/issues/11823

[octavia-bot]

AI Triage Starting...

Thank you for opening this issue! I'm an AI assistant that will do an initial review and may:

• Ask clarifying questions if needed
• Suggest relevant documentation or workarounds
• Flag this for internal visibility

Note: Community issues are reviewed on a best-effort basis and do not have a guaranteed response time. For additional help:

• Join the Airbyte Community Slack to connect with other users and community members
• If you're an Airbyte Cloud customer, you can open a support ticket or contact your account representative, referencing this issue URL

View playbook

• 🔗 Session URL: https://app.devin.ai/sessions/2ef3a4e7ec224e23a09e17ca741e9f3f

✅ Devin AI session created successfully!

[devin-ai-integration]

Hi Yunus Kursav (@ykursav), thank you for reporting this issue!

I can see from the traceback that the source-sftp-bulk connector (v1.9.0) is raising a CheckAvailabilityError because get_files() returned no results for your configured stream. The error occurs during the connection check step when the connector tries to list files matching your configuration.

A few clarifying questions that would help narrow this down:

1. Folder path: What folder path are you configuring? Is it an absolute path (e.g., /home/user/data/) or relative? Does the SFTP user have read permissions on that directory?
2. Glob pattern: What glob pattern(s) are you using? For example, **/*.csv or a specific pattern?
3. Start date: Do you have a start_date configured? If so, are the files on the SFTP server modified after that date? The connector only picks up files modified after the start date.
4. Are you using Airbyte Cloud or OSS? And if OSS, which platform version?
5. File details: Roughly how many files are in the target directory, and what format are they (CSV, JSON, Parquet, etc.)?

You mentioned that the standard SFTP connector works — that confirms basic connectivity is fine. The difference is that source-sftp-bulk uses glob-based file discovery and has a start_date filter, so the issue is likely in how files are being matched.

Troubleshooting Steps

1. Try a broad glob pattern first: Set the glob pattern to ** or **/* to match all files, and ensure no start_date is set (or set it far in the past). This helps determine if the issue is with pattern matching vs. directory access.
2. Check folder path format: The folder path should be the absolute path on the SFTP server (e.g., /upload/data). Do not include the hostname or protocol prefix.
3. Verify file permissions: Ensure the SFTP user has read access to both the directory and the files within it. Some SFTP servers restrict directory listing.
4. Check for symlinks: If the target directory or files are symlinks, the connector may not follow them.

I have flagged this for internal review as it may indicate a connector-level issue with file discovery.

---

Need more help? Join Airbyte Community Slack for peer support, or if you're a Cloud customer, open a support ticket referencing this URL.

[devin-ai-integration]

This issue is being tracked internally: https://github.com/airbytehq/oncall/issues/11823

[ameliafoster203-rgb]

Thanks for flagging this! Following the internal tracking: airbytehq/oncall#11823

…

On Mon, Mar 30, 2026, 3:50 PM devin-ai-integration[bot] < ***@***.***> wrote: *devin-ai-integration[bot]* left a comment (airbytehq/airbyte#75625) <#75625 (comment)> This issue is being tracked internally: airbytehq/oncall#11823 <https://github.com/airbytehq/oncall/issues/11823> — Reply to this email directly, view it on GitHub <#75625?email_source=notifications&email_token=B72GLV4SIH6DPWRDEUAD53T4TLFYTA5CNFSNUABFM5UWIORPF5TWS5BNNB2WEL2JONZXKZKDN5WW2ZLOOQXTIMJVG43TIMJVGEZ2M4TFMFZW63VKON2WE43DOJUWEZLEUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#issuecomment-4157741513>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/B72GLV7DOYKWZAFOMN57EAD4TLFYTAVCNFSM6AAAAACXGWOA5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DCNJXG42DCNJRGM> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>