> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# General Troubleshooting

> Common issues and solutions for the Elementum platform, including bulk imports on Snowflake-backed objects and GraphQL API configuration.

Use this guide to diagnose and resolve common issues on the Elementum platform. If your issue is not covered here, contact [Elementum Support](https://elementum.ai/support).

## Bulk Import on Snowflake-Backed Objects

To bulk import on an object that is based on a Snowflake table, Elementum must be granted the correct permissions to create and update records in Snowflake. If these permissions are missing, the import will continue to fail silently — no error is displayed in Elementum.

<Steps>
  <Step title="Verify Snowflake Permissions">
    Confirm that the Elementum service account has been granted `CREATE` and `UPDATE` privileges on the target Snowflake table.
  </Step>

  <Step title="Retry the Import">
    Once the correct permissions are in place, re-run the bulk import.
  </Step>
</Steps>

### Resolving "String is too long and would be truncated" Errors

When writing to a Snowflake-backed object, you may see an error like:

```
DML operation to table <TABLE_NAME> failed on column <COLUMN_NAME> with error:
String '<VALUE>' is too long and would be truncated
```

This means the value being written is longer than the maximum length defined for that column in Snowflake. Snowflake does not truncate data automatically — it rejects the operation instead.

<Steps>
  <Step title="Identify the Column and Value">
    Note the column name and the specific value referenced in the error message. These tell you exactly which field is too long.
  </Step>

  <Step title="Locate the Source of the Value">
    Trace the value back to its source — for example, the record being imported, the field mapping in your automation, or the upstream Data Mine query.
  </Step>

  <Step title="Shorten or Remove the Value">
    Update the source data so the value fits within the column's character limit, then retry the operation. For automations, review the field mapping to confirm the source field's values stay within the expected length.
  </Step>

  <Step title="Confirm or Increase the Column Length">
    If shortening the value is not an option, reach out to a database administrator with access to `information_schema.columns` and ask them to confirm the column's defined maximum length:

    ```sql theme={null}
    SELECT
        table_schema,
        table_name,
        column_name,
        character_maximum_length AS defined_max_characters
    FROM information_schema.columns
    WHERE table_name = 'YOUR_TABLE_NAME'
      AND column_name = 'YOUR_COLUMN_NAME';
    ```

    The same administrator can typically increase the column length in Snowflake if a larger limit is required.
  </Step>
</Steps>

## Triggering a GraphQL API

To trigger a GraphQL API from Elementum, configure the request with the following settings:

<Steps>
  <Step title="Set the Method to POST">
    GraphQL APIs require the `POST` HTTP method.
  </Step>

  <Step title="Enter the GraphQL Endpoint URL">
    Set the URL to the GraphQL endpoint you want to call.
  </Step>

  <Step title="Choose JSON as the Body Format">
    Select **JSON** as the body format and enter the GraphQL payload.
  </Step>

  <Step title="Set the Response Type to JSON">
    Configure the response type as **JSON** to properly parse the result.
  </Step>
</Steps>