From 22bf8fc90f80417fe0f394941441215331f03aa8 Mon Sep 17 00:00:00 2001 From: Paul Cornell Date: Tue, 11 Nov 2025 17:38:46 -0800 Subject: [PATCH 1/3] Additional troubleshooters --- docs.json | 5 +- support/issues/cannot-locate-credentials.mdx | 36 +++++++++++++ .../issues/google-drive-schema-validation.mdx | 52 +++++++++++++++++++ .../no-fast-partitioning-for-images.mdx | 33 ++++++++++++ 4 files changed, 124 insertions(+), 2 deletions(-) create mode 100644 support/issues/cannot-locate-credentials.mdx create mode 100644 support/issues/google-drive-schema-validation.mdx create mode 100644 support/issues/no-fast-partitioning-for-images.mdx diff --git a/docs.json b/docs.json index 195d5565..c95bc058 100644 --- a/docs.json +++ b/docs.json @@ -536,14 +536,15 @@ "group": "Issues", "pages": [ "support/issues/overview", - "support/issues/api-connector-secrets", "support/issues/authorization-permissions", "support/issues/configuration-resource", "support/issues/quota-billing-rate-limiting", "support/issues/network-connection-timeout", "support/issues/data-format-schema-validation", "support/issues/document-processing", - "support/issues/internal-file-handling" + "support/issues/internal-file-handling", + "support/issues/api-connector-secrets", + "support/issues/cannot-locate-credentials" ] } ] diff --git a/support/issues/cannot-locate-credentials.mdx b/support/issues/cannot-locate-credentials.mdx new file mode 100644 index 00000000..e6a95040 --- /dev/null +++ b/support/issues/cannot-locate-credentials.mdx @@ -0,0 +1,36 @@ +--- +title: S3 destination connector - Unable to locate credentials +--- + +## Issue + +When you try to run a workflow in Unstructured, and the workflow contains an Amazon S3 destination connector, +you get an error that contains text similar to one of the following, and the workflow fails to run: + +```text +500: Error in uploader - [NoCredentialsError] Unable to locate credentials +``` + +```text +failed to invoke plugin: Unable to locate credentials +``` + +## Possible causes + +- Unstructured tried to save its processed data to the specific Amazon S3 bucket, but Unstructured could not find the necessary + security keys or other credentials to get access to that bucket. +- The specified AWS Access Key ID and Secret Access Key are missing from your S3 destination connector configuration. +- The specified credentials are incorrect, have been revoked, or have expired. +- The S3 destination connector is configured to use a temporary IAM role, but that role does not have permission to write to the target bucket. + +## Possible solutions + +- Double-check that your workflow's Amazon S3 destination connector has the correct, valid credentials specified. +- Confirm that the specified credentials are still present and valid in your AWS account. +- If your organization uses IAM roles, contact your platform administrator to ensure the role has `s3:PutObject` permissions for the bucket you are trying to use. + +## Additional resources + +- Always copy and paste security keys and other credentials carefully. +- If possible, use your organization's secrets manager to handle security keys and other credentials automatically. +- To ask questions or get additional help with this issue, see [requesting support](/support/request). \ No newline at end of file diff --git a/support/issues/google-drive-schema-validation.mdx b/support/issues/google-drive-schema-validation.mdx new file mode 100644 index 00000000..9967cd7a --- /dev/null +++ b/support/issues/google-drive-schema-validation.mdx @@ -0,0 +1,52 @@ +--- +title: Google Drive schema validation failure +--- + +## Issue + +When you save and test a Google Drive source connector, you get an error that contains text similar to the following: + +```text +Schema validation failure for GoogleDriveConnectionConfig: +Value error, Expecting value: line 1 column 1 (char 0) at +access_config,service_account_key got -----BEGIN PRIVATE KEY----- +... +``` + +Although you can finish creating and saving this connector, the connection test fails, and you cannot successfully run any +workflows that use this failed connector. + +## Cause + +You have configured the Google Drive source connector with the Google Drive service account's key in an incorrect format. +You likely have specified only a portion of the file, such as just the private key part. Unstructured expects the entire contents +of the Google Drive service account's key file. + +## Solution + +1. Find the original Google Drive service account's key file in JSON format, which you downloaded earlier from your Google Cloud account when + you originally created the Google Drive source connector. +2. Open the file in a text editor such as Notepad, Visual Studio Code, or TextEdit. +3. Copy everything in the file, starting from the first opening brace `{` to the final closing brace `}`. +4. In the original Google Drive source connector's settings, delete the original contents of the **Service Account Key** field, and paste + the complete JSON content that you just copied. +5. Save the changes and re-test and re-save the connector. + +## Additional resources + +- If the connector test still fails, try using a tool such as `tr` for macOS or Linux, or PowerShell for Windows, to copy + the entire contents of the file, instead of a text editor, as follows: + + - For macOS or Linux: + + ```text + tr -d '\n' < + ``` + + - For Windows: + + ```text + (Get-Content -Path "" -Raw).Replace("`r`n", "").Replace("`n", "") + ``` + +- To ask questions or get additional help with this issue, see [requesting support](/support/request). \ No newline at end of file diff --git a/support/issues/no-fast-partitioning-for-images.mdx b/support/issues/no-fast-partitioning-for-images.mdx new file mode 100644 index 00000000..4efd5ca9 --- /dev/null +++ b/support/issues/no-fast-partitioning-for-images.mdx @@ -0,0 +1,33 @@ +--- +title: The Fast strategy is not available for image files +--- + +## Issue + +When you try to run a workflow in Unstructured with the following settings: + +- The workflow contains a **Partitioner** node set to use the **Fast** partitioning strategy. +- The workflow is configured to process an image file, such as a PNG or JPG file. + +You get an error that contains text similar to the following, and the workflow fails to run: + +```text +422: Error in partition - {"detail":"The fast strategy is not available for image files"} +``` + +## Cause + +Unstructured is trying to process an image file—such as a PNG or JPG file—by using the **Fast** partitioning strategy, but +this strategy is designed for text-based documents only and cannot analyze the layout of images. + +## Solution + +1. Change the workflow's**Partitioner** node's **Partition Strategy** setting to **Auto**, **High Res**, or **VLM**. +2. Re-run the workflow. + +## Additional resources + +- If your workflow is configured to process a mixture of file types, you should use the **Auto** partitioning strategy. Unstructured will then + automatically choose the best partitioning strategy for each file. +- Learn more about the various [partitioning](/ui/partitioning) strategies. +- To ask questions or get additional help with this issue, see [requesting support](/support/request). \ No newline at end of file From e41f8526432d9d095667004ebb64d3cc7a47356f Mon Sep 17 00:00:00 2001 From: Paul Cornell Date: Wed, 12 Nov 2025 17:13:22 -0800 Subject: [PATCH 2/3] Added more troubleshooters --- .../issues/get-authenticated-user-error.mdx | 32 +++++++++++++++++++ support/issues/workflow-job-in-progress.mdx | 28 ++++++++++++++++ 2 files changed, 60 insertions(+) create mode 100644 support/issues/get-authenticated-user-error.mdx create mode 100644 support/issues/workflow-job-in-progress.mdx diff --git a/support/issues/get-authenticated-user-error.mdx b/support/issues/get-authenticated-user-error.mdx new file mode 100644 index 00000000..b87107dc --- /dev/null +++ b/support/issues/get-authenticated-user-error.mdx @@ -0,0 +1,32 @@ +--- +title: Get authenticated user error +--- + +## Issue + +When you try to sign in to Unstructured, you get an error that contains text similar to the following: + +```text +Error in getAuthenticatedUser +``` + +This error can prevent you from accessing your +Unstructured account dashboard or performing other actions in your Unstructured account. + +## Possible causes + +- Unstructured is having trouble verifying your login session. +- Your Unstructured login session has expired. +- Your web browser's cache or cookies are causing some kind of conflict. +- There is a temporary issue with Unstructured's authentication service. + +## Possible solutions + +- Log out of your Unstructured account completely, if you can. To do this, in the Unstructured user interface, on the sidebar, + click your user icon, and then click **Logout**. +- Clear your web browser's cache and cookies for the Unstructured website. +- Close and then reopen your web browser, and then try to sign in again to your Unstructured account. + +## Additional resources + +To ask questions or get additional help with this issue, see [requesting support](/support/request). \ No newline at end of file diff --git a/support/issues/workflow-job-in-progress.mdx b/support/issues/workflow-job-in-progress.mdx new file mode 100644 index 00000000..9647c823 --- /dev/null +++ b/support/issues/workflow-job-in-progress.mdx @@ -0,0 +1,28 @@ +--- +title: Workflow already has a job scheduled or in progress +--- + +## Issue + +When you try to run a workflow, you get a warning message that contains text similar to the following: + +```text +Failed to schedule job for workflow ... Workflow already has a job scheduled or in progress. Retrying in 60 seconds. +``` + +## Causes + +- Unstructured tried to start a new job run for the workflow, but the previous job run for that workflow is stuck or has otherwise not finished yet. +- The workflow's schedule is too frequent for how long the job takes to run. For example, the workflow might be scheduled to + run every 5 minutes, but each job run for that workflow typically takes 10 minutes or longer to complete. + +## Solutions + +- Unstructured will wait and try the new job run again in 60 seconds. +- Check previous job runs for the workflow to see if any of them are stuck. If so, try to cancel them. +- Check previous job runs for the workflow to see if any of them seem to be running much longer than usual. If so, + consider adjusting the workflow's schedule to run less frequently. Or, temporarily turn off the workflow's schedule and then run the workflow manually as needed. + +## Additional resources + +To ask questions or get additional help with this issue, see [requesting support](/support/request). \ No newline at end of file From e986fe013ba4f4c47a9472883450f63048319eda Mon Sep 17 00:00:00 2001 From: Paul Cornell Date: Wed, 12 Nov 2025 19:52:25 -0800 Subject: [PATCH 3/3] Fix typo. Add files to TOC --- docs.json | 6 +++++- support/issues/no-fast-partitioning-for-images.mdx | 2 +- 2 files changed, 6 insertions(+), 2 deletions(-) diff --git a/docs.json b/docs.json index c95bc058..c9f17849 100644 --- a/docs.json +++ b/docs.json @@ -544,7 +544,11 @@ "support/issues/document-processing", "support/issues/internal-file-handling", "support/issues/api-connector-secrets", - "support/issues/cannot-locate-credentials" + "support/issues/cannot-locate-credentials", + "support/issues/get-authenticated-user-error", + "support/issues/workflow-job-in-progress", + "support/issues/no-fast-partitioning-for-images", + "support/issues/google-drive-schema-validation" ] } ] diff --git a/support/issues/no-fast-partitioning-for-images.mdx b/support/issues/no-fast-partitioning-for-images.mdx index 4efd5ca9..ff32e122 100644 --- a/support/issues/no-fast-partitioning-for-images.mdx +++ b/support/issues/no-fast-partitioning-for-images.mdx @@ -22,7 +22,7 @@ this strategy is designed for text-based documents only and cannot analyze the l ## Solution -1. Change the workflow's**Partitioner** node's **Partition Strategy** setting to **Auto**, **High Res**, or **VLM**. +1. Change the workflow's **Partitioner** node's **Partition Strategy** setting to **Auto**, **High Res**, or **VLM**. 2. Re-run the workflow. ## Additional resources