> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/studio/getting-started/troubleshooting.md). # Troubleshooting This page covers the most common issues you may encounter while using Origin Studio. Each article is structured to help you identify the problem, understand what might be causing it, and resolve it yourself where possible. If your issue is not listed here or the resolution steps do not solve the problem, contact your Fabric Data account team using the details at the bottom of this page. *** ### Why Can't I Edit This Record? #### Symptoms * You can open a title record but all fields are greyed out or read-only. * You see an "Insufficient permissions" message when attempting to save changes. * Some fields are editable but others are locked on the same record. #### Possible Causes **Your role does not include edit permissions.** Your administrator has assigned you a role that allows viewing but not editing. This is common for Reviewer or Viewer roles. **The record is in a workflow stage that restricts editing.** Origin Studio can lock records at certain workflow stages — for example, once metadata has been approved or submitted for delivery. Editing may only be available in earlier stages. **Field-level permissions are restricting specific fields.** Even if your role allows general editing, certain fields may be restricted to specific teams or roles. For example, legal classification fields may only be editable by users with a Legal role. **Another user has the record open.** If your tenant has concurrent editing controls enabled, another user may currently be editing the same record. #### Resolution Steps 1. Check your role by going to your profile or asking your administrator to confirm your assigned permissions. 2. Check the workflow stage displayed on the record. If the record has been approved or is in a locked stage, it may need to be moved back to an editable stage by a user with the appropriate permissions. 3. If only specific fields are locked, ask your administrator whether field-level permissions are applied to those fields for your role. 4. If you suspect another user has the record open, wait a few minutes and try again. #### When to Contact Support Contact support if your role and workflow stage both appear correct but editing is still blocked, or if you see an error message that does not match the scenarios above. *** ### Why Can't I See This Title? #### Symptoms * A colleague has shared a title name or ID with you, but it does not appear in your catalogue view. * Search returns no results for a title you know exists in the system. * You can see fewer titles in a catalogue than you expected. #### Possible Causes **Your role restricts catalogue or territory visibility.** Administrators can scope roles so that users only see titles within specific catalogues, territories, or business units. If the title belongs to a catalogue you do not have access to, it will not appear in your view. **The title has not been assigned to your catalogue.** The title may exist in Origin Studio but has not yet been added to the catalogue you are browsing. **Active filters are hiding the title.** A saved or active filter on your current view may be excluding the title from your results. **The title has been archived or soft-deleted.** If a title has been removed from active use, it may no longer appear in default search results. #### Resolution Steps 1. Clear all active filters and search again using the title name or unique identifier. 2. Try searching across all catalogues rather than within a specific one, if your permissions allow it. 3. Ask a colleague with broader access to confirm the title exists and which catalogue it sits in. 4. Ask your administrator to check whether your role includes visibility for the relevant catalogue or territory. #### When to Contact Support Contact support if your administrator confirms you should have access but the title still does not appear, or if the title cannot be found by any user in the system. *** ### Why Is My Integration Failing? #### Symptoms * An API call to Origin Studio returns an error response (e.g., 401, 403, 404, or 500). * Data that should be flowing from Origin Studio to a downstream system is not arriving or is arriving incomplete. * An automated workflow or event notification has stopped triggering. #### Possible Causes **Your API key has expired or been revoked.** API keys in Origin Studio have configurable expiration dates. If a key has expired, all requests using that key will fail with an authentication error. **The API key does not have the required permissions.** API keys are scoped to specific actions and data. If the integration is attempting to access a resource outside the key's permission scope, the request will be rejected. **The endpoint URL or payload structure has changed.** If Origin Studio has been updated and your integration references a deprecated endpoint or uses an outdated request format, calls may fail. **Network or firewall issues.** Your downstream system may be unable to reach Origin Studio due to a network configuration change, firewall rule, or DNS issue on your side. **Rate limiting.** If your integration is sending a high volume of requests in a short period, it may be hitting the API rate limit. #### Resolution Steps 1. Check the error response code and message. A 401 or 403 typically points to an authentication or permissions issue. A 404 suggests the endpoint or resource does not exist. A 429 indicates rate limiting. A 500 is a server-side error. 2. Verify your API key is still active and has not passed its expiration date. You can check this in the API Key Management section of the admin area. 3. Confirm the key's permission scope covers the resources and actions your integration requires. 4. Review the Origin Studio API documentation or recent release notes for any changes to endpoints or payload formats. 5. Test the connection independently — for example, using a tool like Postman or cURL — to isolate whether the issue is in your integration code or in the network path. 6. If you suspect rate limiting, review your request frequency and implement backoff logic if needed. #### When to Contact Support Contact support if you are receiving 500-series errors consistently, if your API key appears valid but authentication still fails, or if event notifications have stopped firing without any configuration change on your side. *** ### Why Is This Schedule Conflicting? #### Symptoms * You receive a conflict warning when setting or updating an availability window or delivery schedule for a title. * A title appears in two overlapping schedules and the system flags an error. * A scheduled delivery did not execute because it was blocked by a conflict. #### Possible Causes **Overlapping availability windows.** The title has been assigned availability dates that overlap with an existing window for the same platform, territory, or partner. Origin Studio flags this to prevent contradictory delivery instructions. **Duplicate schedule entries.** The same title-platform-territory combination has been scheduled more than once, potentially by different users or through separate import batches. **Timezone misalignment.** If your team operates across multiple timezones, a schedule that appears non-overlapping in one timezone may conflict when evaluated in the system's reference timezone. **Inherited schedules from a parent record.** If the title inherits scheduling from a series or season-level record, the inherited dates may conflict with an override set at the title level. #### Resolution Steps 1. Open the title record and review all active schedules. Identify where the overlap or duplication occurs. 2. Check whether the conflict is between two manually created schedules or between a manual entry and an inherited one. 3. If the conflict is a genuine duplication, remove or adjust the redundant schedule entry. 4. If the conflict is caused by timezone differences, confirm which timezone the system is using and adjust your dates accordingly. 5. If the schedule was created by an automated import, review the import source data for duplicates before re-importing. #### When to Contact Support Contact support if the system flags a conflict but you cannot identify any overlapping entries, or if inherited schedules are conflicting in ways you cannot resolve from the title-level record. *** ### Why Are My Changes Not Appearing? #### Symptoms * You saved changes to a title record but the updated values are not showing for other users. * An export or API response returns older data than what you see in the UI. * A recently created title does not appear in search results. #### Possible Causes **Caching or indexing delay.** After a change is saved, it may take a short time for the updated data to propagate to search indexes and API responses. This is usually seconds but can occasionally take longer during high-volume operations. **The changes were saved as a draft.** Some workflow configurations allow changes to be saved in a draft state that is only visible to the author until it is submitted or approved. **Filters or views are masking the update.** Other users may have active filters or saved views that exclude the updated record based on its current field values. **A data migration or bulk operation is in progress.** During large-scale imports or migrations, search indexes may temporarily lag behind the latest data. #### Resolution Steps 1. Wait a few minutes and refresh the page or re-run the search. 2. Check whether the record is in a draft or pending state that limits its visibility to other users. 3. Ask the affected user to clear their filters and refresh their view. 4. If a bulk import or migration is currently running, wait for it to complete before expecting full consistency. #### When to Contact Support Contact support if changes remain invisible to other users or API consumers after 15 minutes, or if you suspect a data sync issue between the UI and the underlying database. *** ### Why Was My Import Rejected? #### Symptoms * A CSV or bulk import returned errors and some or all records were not imported. * The import completed but field values are missing or incorrect on the imported records. * You received a validation error referencing specific rows or fields. #### Possible Causes **The file format does not match the expected template.** Origin Studio expects a specific column structure for CSV imports. Missing columns, renamed headers, or an incorrect delimiter will cause validation failures. **Required fields are empty.** If your metadata model includes required fields, any row missing a value for those fields will be rejected. **Picklist values do not match.** If a field uses a controlled vocabulary, imported values must exactly match the allowed options — including capitalisation and spacing. **Character encoding issues.** Files saved with non-UTF-8 encoding may produce garbled characters or validation errors on special characters, accents, or non-Latin scripts. **Duplicate identifiers.** If the import file contains rows with duplicate unique identifiers, the system may reject the duplicates or overwrite existing records depending on your import settings. #### Resolution Steps 1. Download the error report provided after the import. It will identify which rows failed and why. 2. Compare your file's column headers against the expected import template available in the admin area. 3. Check failed rows for empty required fields, mismatched picklist values, or encoding issues. 4. Re-save your file as UTF-8 encoded CSV if you suspect a character encoding problem. 5. Remove or de-duplicate any rows with duplicate identifiers before re-importing. #### When to Contact Support Contact support if the error report does not provide enough detail to identify the issue, if the import fails silently with no error output, or if correctly formatted rows are still being rejected. *** ### Still Need Help? If your issue is not covered here or the resolution steps did not solve the problem: * **Check the release notes** — your issue may relate to a recent update. See Release Notes for the latest changes. * **Contact your Fabric Data account team** — they can investigate tenant-specific configuration issues and escalate to engineering if needed. * **Submit a support request** — use the service desk portal to log a ticket with a description of the issue, the steps you have already tried, and any error messages or screenshots.