Share & Print
You know when KOSMA saves your work, when the others see it and what to do when KOSMA asks about unsaved changes.
KOSMA saves your work by itself, about one second after each change, and sends it to the server in the same step. You do not have to save, and everyone who works in the budget sees your change.
In an open dialog with **Cancel**, KOSMA saves your input when you close the dialog with **Ok**.
You can still save by hand: choose **Save Project** in the **Project** menu, or press ⌘S or Ctrl+S. In KOSMA in the browser, click **Save** at the bottom of the left rail. KOSMA confirms:
Project saved and synced
KOSMA never sends a read-only budget to the server: a budget shared with you as **Can view**, any budget on a Free licence, and any budget while you are signed out.
In the budget dropdown of the left rail, a dot after a budget's name means that work on this computer has not reached the server yet. The dot appears when a change is not saved yet, the budget was never uploaded, an upload failed, or you are offline. Because KOSMA saves by itself, the dot is normally gone after about a second. Point at the dot to see:
Not on the server yet
If KOSMA could not send the budget, the message at the dot gives the reason instead. If KOSMA will retry by itself, it reads:
Saved locally — sync failed, will retry.
If the message names one of the reasons below, the server refuses the budget every time. Your changes stay on this computer, and KOSMA no longer sends them by itself. What you can do:
- Your licence does not cover the module: upgrade your licence, or ask your team admin if your licence comes from a team. - The budget is shared with you to view only: ask the person who created it, or the project owner, for **Can edit**. - Your access to the budget was removed: the changes you made after that stay only on this computer.
If the budget is shared with you again, KOSMA replaces your copy with the version of the person who shares it. The changes you made after your access was removed are lost.
Once your licence covers the module, or you have **Can edit**, KOSMA sends the budget with your next change. A project that is archived because its owner's account is inactive works differently, see [how sharing works](/kb/article/how-sharing-works).
In the **Budgets Manager**, the **Status** column shows **Not uploaded** and **retry** for a budget that never reached the server or whose upload failed. **retry** sends the budget again. KOSMA also sends such a budget by itself when the connection returns, and when you open or select the budget.
If the server refused the upload and will refuse it again, the column shows **Not uploaded · refused** and no **retry**. Point at it to see:
The server refused this upload and will refuse it again: your licence does not cover this module, or this budget is shared with you to view only.
To upgrade your licence, see [upgrade your licence](/kb/article/upgrade-your-licence).
Before you share a budget or switch to another computer, check that the budget shows no dot and no **Not uploaded**. Other people and your other computer get only what has reached the server.
If the server has a newer version and nothing on this computer is waiting to be sent, KOSMA loads the newer version without asking. If this computer also has changes that have not reached the server, KOSMA opens **Dataset Version Conflict**.
**Discard Changes** deletes the changes on this computer that have not reached the server. You cannot get them back.
To keep your work, click **Save Changes**. KOSMA puts your changes into a new budget whose name ends in **(conflict copy)**, then loads the version from the server. **Discard Changes** loads the version from the server without your changes.
If the server is missing changes to a budget, KOSMA keeps the version on this computer and shows:
The server copy of this file is incomplete from revision {Revision}, so this device can't load the latest changes. Your local copy is safe. Contact KOSMA support.
The revision is the saved state from which changes are missing. Give it to support.
If KOSMA cannot reach the server, it saves your work on this computer and shows one of these messages:
Saved locally — offline, will sync when reconnected.
Without a connection, you cannot edit the cells of a shared budget. Local-only mode is a different state: KOSMA reaches the server, but your stored sign-in is no longer valid. Local-only mode does not end by itself. To tell the two apart, and for what you can still edit offline, see [work offline or in local-only mode](/kb/article/work-offline-or-in-local-only-mode).
KOSMA asks about unsaved changes only if your last edit was less than about a second ago. Anything older is already saved. If you close a project window at that moment, KOSMA opens **Close project**. **Save**, **Don't Save** and **Cancel** apply to this one project. If you see this dialog although you wanted to quit KOSMA, you have closed only one project window.
If you quit KOSMA or close the Project Manager, KOSMA asks once for all open projects. The **Unsaved changes** dialog lists every project with unsaved changes. **Save All**, **Discard All** and **Cancel** apply to all of them at once.
**Don't Save**, **Discard** in the **Project** menu and **Discard All** drop only what KOSMA has not saved yet, which is usually little or nothing. They do not undo saved changes. A cell can still show the dropped value for a moment, then it shows the saved value.
If you sign in on a second computer, KOSMA ends your session on the first one without asking. Soon after, KOSMA saves every open project on the first computer, without sending it to the server, and shows the sign-in screen with this message:
Your session was ended (signed in elsewhere or ended by an administrator). Your work was saved on this machine and you have been signed out.
When you sign in on the first computer again and open the budget, KOSMA sends that work to the server. If the budget changed on the server in the meantime, KOSMA opens **Dataset Version Conflict**. If KOSMA cannot save your work on the first computer, it does not sign you out. It stays in [local-only mode](/kb/article/work-offline-or-in-local-only-mode) and shows:
Your session was ended (signed in elsewhere or ended by an administrator), but your work could not be saved. Your work is still open here — log in again, then save it.
Click  **Log In Again** in the left rail and sign in. Then save your work.
Markdown