## Connection and authentication issues

URL: https://docs.atlan.com/apps/connectors/etl-tools/talend/troubleshooting/connection-and-authentication-issues

> Resolve repository access failures and authentication errors for the Talend connector

Use these steps to resolve common repository access failures, authentication errors, and missing asset issues when running the Talend connector workflow in Atlan.

## Repository connection failure

::::danger Error
**`Connection failed` or `Repository not found`**
::::

### Cause

The workflow fails during connection when the repository URL is incorrect, the repository doesn't exist, or Atlan can't reach the repository host.

### Solution

1. Verify the repository URL format matches your hosting platform:
 - GitHub: `https://github.com/organization/repository`
 - Stash: `https://stash.company.com/scm/project/repository`
2. Confirm the repository exists and contains Talend project files.
3. Verify Atlan has network access to your repository host. For on-premises Stash deployments, check firewall rules and VPN configurations.

---

## Authentication failure

::::danger Error
**`Authentication failed` or `401 Unauthorized`**
::::

### Cause

The workflow fails during authentication when the personal access token is invalid, expired, or lacks required permissions.

### Solution

1. Verify the personal access token is valid and not expired.
2. Confirm the token has the correct permissions:
 - GitHub: `repo` scope for private repositories or `public_repo` for public repositories
 - Stash: **Read** permissions for both project and repository
3. Copy and paste the token carefully with no extra spaces.
4. If the token was revoked, generate a new token and update the workflow configuration.

---

## Missing assets or incomplete metadata

:::warning Error
**Expected jobs or components not appearing in Atlan**
:::

### Cause

The workflow completes but assets are missing when the repository doesn't contain the expected Talend project structure or the branch configuration is incorrect.

### Solution

1. Verify `.item` and `.properties` files exist in the repository.
2. Confirm the workflow points to the correct branch, for example `main`, `master`, or `develop`.
3. Check that the folder structure matches the Talend project export format from Talend Studio.
4. If you specified a **Talend project path**, verify the subdirectory path is correct.

---

## Incomplete metadata for child jobs

::::danger Error
**Child job appears in Atlan without its expected properties metadata**
::::

### Cause

The connector doesn't support parent-child job relationships. It processes each job independently and resolves the properties file using the job's own name and project details, so a properties file that's only reachable through the parent job reference isn't found.

This applies to job references within a single project and to references that cross project boundaries. Cross-project references are affected most when you catalog Talend projects as separate Atlan connections, because the connector resolves properties files within the project it's processing and can't follow a reference into another project or connection.

### Solution

1. Identify the job name and project the connector processes for the child job.
2. Confirm a matching `.properties` file exists for that job name and project, rather than only under the parent job or parent project.
3. Add the properties file at the location matching the actual job and project information, then re-run the workflow.

For jobs that reference other projects, repeat these steps in each project that the connector processes. A properties file in one project doesn't resolve a reference from another project.

---

## See also

- [Set up Talend](https://docs.atlan.com/llms/connectors/talend/set-up-talend/llms.txt): Configure GitHub or Stash access tokens for the Talend connector
- [Crawl Talend assets](https://docs.atlan.com/llms/connectors/talend/crawl-talend/llms.txt): Create the workflow and run the crawl

## Need help

If you need assistance after trying these steps, contact Logan Data support by [submitting a ticket](https://logandata.com/submit-a-ticket/).

---