# Handling export conflicts for unsaved projects

When you create and export a canvas without signing in, the project is automatically assigned a **project ID**. If you come back the next day and create a new canvas, but you’re not signed in again, the new canvas will be assigned a **different project ID**. If you try to export this new canvas to the IDE project from the first day, you will encounter a conflict, as the project IDs don't match.

If you were not signed in on **Day 1** and did not save the project link (since the canvas is tied to the browser session), you may lose access to your previous project, making it impossible to export directly into the IDE project from Day 1.

## How the Conflict is Handled

When you attempt to export a new canvas on Day 2 and the system detects a mismatch in project IDs (as outlined in the warning message), it will also display a link to the **lost canvas** from Day 1. This lost canvas is still accessible, tied to the IDE project ID from the first day.

### Step-by-Step Resolution:

#### 1. **Click the Canvas Link in the Warning**:

* In the warning message, click on the link labelled **"Recently Imported Canvas"**.
* This will open the **non-signed-in editor** with the unsaved canvas from Day 1.

<figure><img src="/files/3SzSQ9y5YVaXtHs0fDJ3" alt=""><figcaption><p>VS Code Terminal: In the warning message, click on the link labelled <strong>"Recently Imported Canvas"</strong> to access the unsaved canvas</p></figcaption></figure>

#### 2. **Rename and Save the Canvas**:

* In the editor, rename the canvas to give it a proper title.
* Sign in to your JSX.Design account to save the canvas to your profile.

#### 3. **Access Your Projects**:

* Click the **Home button** on the top-left corner of the editor. This will take you to the project dashboard.
* You will now see the newly saved canvas under an **Unnamed project**.

#### 4. **Create a New Canvas in the Same Project**:

* Inside the project dashboard, click on the **Unnamed project**.
* From here, you can create a new canvas under this project, redo any work you intended to do on Day 2, and export it without any conflict.

### Conclusion

By following these steps, you can resolve any project ID conflicts and keep your work organized under a single project. To avoid these issues in the future, we recommend signing in before starting a new session, ensuring that your projects are properly saved and linked.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://skyslit.gitbook.io/jsx.design/troubleshooting/handling-export-conflicts-for-unsaved-projects.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.