# Troubleshooting

Below, you will find a comprehensive list of common issues users may encounter, accompanied by solutions to resolve them.

To access the logs for Marker Data, navigate to the Help menu and select Open Logs.

To ensure optimal functionality of Marker Data, please ensure it is installed within the Applications folder.

The slow upload speed to Notion could be attributed to potential issues with Notion's servers or regional server connectivity. Please verify the current status of Notion's servers.

Please ensure that you are using Marker Data's Share Destination. Images will not be extracted when using Marker Data's Workflow Extension.

When Marker Data displays a Failed to complete upload error, it may be attributed to various underlying causes. If you are utilising a firewall application such as Little Snitch, please ensure that outgoing connections to Marker Data are permitted.

If you encounter issues uploading to your Notion Database, please follow these steps to troubleshoot:

1. Navigate to the Help menu and select Open Logs.
2. Open the log file csv2notion-neo_log.txt.
3. Scroll down to review the most recent entries.

If you observe the error messages HTTPError: 401 Client Error: Unauthorized for url or Invalid Notion token, it is likely that either your Notion Database URL is incorrect or your Notion v2 Token has expired. For detailed instructions on resolving these issues, please refer to the Notion Prerequisite documentation.

If you encounter issues uploading to your Airtable Database, please follow these steps to troubleshoot:

1. Navigate to the Help menu and select Open Logs.
2. Open the log file airlift_log.txt.
3. Scroll down to review the most recent entries.

If you observe the error messages Authentication required or Invalid permissions, or the requested model was not found., it is likely that either your Airtable Token is incorrect or your Airtable Base ID & Table ID is incorrect. For detailed instructions on resolving these issues, please refer to the Airtable Prerequisite documentation.

If you observe the error message Error in call to API function "files/create_folder": Your app is not permitted to access this endpoint because it does not have the required scope \'files.content.write\'. The owner of the app can enable the scope for the app using the Permissions tab on the App Console.'), it is likely that the required scopes for the app utilising the Permissions tab within the Dropbox's App Console is not checked. For detailed instructions on resolving these issues, please refer to the Dropbox Prerequisite documentation. After you have checked your and submitted the scopes, you must to re-create and start over your Dropbox refresh token again. For detailed instructions on resolving these issues, please refer to the Creating Airtable Database Profile documentation.

When Marker Data displays a Failed to upload completely error, it may be due to couple of factors. One potential cause is that you are using an Intel-based Mac, which is not supported by Marker Data. Starting with Marker Data version 1.1.0, application is exclusively build and optimised for Apple Silicon only. For further information, please refer to this FAQ.

If you are utilising a firewall application such as Little Snitch, please ensure that outgoing connections to Marker Data are permitted.

Metaburner’s Custom Title is a highly complex title effect, leading to an intricate FCPXML structure. This complexity is the primary reason Final Cut Pro encounters stability issues during the extraction process. Additionally, Marker Data does not account for Metaburner’s Custom Title, as we do not support third-party custom titles for parsing.

If you need to burn Metaburner’s Title into your clips for image extraction via Marker Data, a simple solution is to pre-render the timeline. To do this, render the timeline containing Metaburner’s Title and export it as a new file. Then, create a new timeline with the rendered file and copy-paste the title containing all your markers. This approach allows you to perform extraction tasks seamlessly without encountering any issues.

1. Navigate to the Help menu and select Open Logs.
2. Open the log file csv2notion-neo_log.txt.
3. Scroll down to review the most recent entries.

If you encounter error messages similar to the one displayed, it may indicate that Notion has updated its APIs, requiring an update to Marker Data's Notion module.

2025-02-15 10:23:02,118 [ERROR   ] Error at division
Traceback (most recent call last):
  File "csv2notion_neo/cli.py", line 58, in cli
  File "csv2notion_neo/cli_steps.py", line 80, in upload_rows
  File "tqdm/std.py", line 1181, in __iter__
  File "csv2notion_neo/utils_threading.py", line 39, in process_iter
  File "csv2notion_neo/utils_threading.py", line 39, in <genexpr>
  File "concurrent/futures/_base.py", line 437, in result
  File "concurrent/futures/_base.py", line 389, in __get_result
  File "concurrent/futures/thread.py", line 57, in run
  File "csv2notion_neo/utils_threading.py", line 27, in worker
  File "csv2notion_neo/notion_uploader.py", line 33, in upload_row
  File "csv2notion_neo/notion_uploader.py", line 50, in _get_db_row
  File "csv2notion_neo/notion_db.py", line 106, in add_row
  File "csv2notion_neo/notion_db_collection.py", line 39, in add_row_block
  File "csv2notion_neo/notion_db_collection.py", line 69, in _add_row_block
  File "csv2notion_neo/notion_row.py", line 46, in icon
  File "csv2notion_neo/notion_row_upload_file.py", line 21, in upload_filetype
  File "csv2notion_neo/notion_row_upload_file.py", line 41, in upload_file

Occasionally, Marker Data's Notion module would become non-functional when Notion updates its APIs. This occurs due to the reliance on unofficial APIs.

If you encounter such an problem, please open an issue. With time and thorough investigation, we will release an update for Marker Data. However, the update may not be immediate, as it depends on our availability to analyse and resolve the issue. We appreciate your patience and understanding.

To streamline our internal testing process, we have implemented an automated weekly validation of Marker Data’s module.

Modules	Status	Schedule
Notion		Scheduled weekly on Saturdays at 8:00 AM Singapore time

If the badge is green, indicating a successful test, it confirms that our modules are compatible with the supported database platforms. However, if the badge turns red, signalling a failure, an update may be necessary to ensure continued compatibility.