Save your changes

How saving works on the service page: when the Save button appears, what it stores, and what happens to callers of a published service when you save.

What saving does

Saving stores your working copy of the service, the draft. It does not change what callers get. Callers of a published service keep getting the published version until you publish again; see Publish, republish and unpublish.

How to save

1. Change something on the service page: a cell in the workbook, an input or output, a setting, the AI definition, or an app setting.
2. The button at the top right turns into Save (Speichern). It takes the place of Publish or Published as long as there are unsaved changes.
3. Click Save. A message confirms what was stored: "Configuration saved successfully!", "Workbook saved successfully!" or "Configuration and workbook saved successfully!".

When nothing has changed, there is no Save button; the button shows Publish (Veröffentlichen) or Published (Veröffentlicht) again.

What is saved

• The workbook: sheets, values, formulas and formats.
• Inputs, outputs and AI areas, with their names, titles, types and rules.
• The settings: service name, description, Excel export and caching. See Service settings.
• The AI definition and the app settings (web app, theme).

Only the part that changed is sent. A large workbook can take a moment; a progress window shows the steps.

Leaving with unsaved changes

If you leave the service page with unsaved changes, a dialog Unsaved Changes (Ungespeicherte Änderungen) asks what to do:

• Stay (Bleiben) keeps you on the page so you can save.
• Leave without saving (Ohne Speichern verlassen) drops the changes.

Closing or reloading the browser tab shows the browser's own warning for the same reason.

Save before you publish

Publishing, republishing and unpublishing work on the saved state. With unsaved changes the app answers "Please save your changes before publishing" (or "... before republishing", "... before unpublishing"). Save first, then publish.

Limits

• The workbook must be loaded before it can be saved. If the app says "Please wait for the workbook to load before saving", wait a moment and click Save again.
• Each plan has a workbook size limit. When a save would go over it, the save is refused and the message names the size and the limit. See File size limits.
• While a save is running, a second click answers "Save already in progress".

Related

• Test before publishing
• Publish, republish and unpublish
• Core concepts

For developers and agents

• Saving changes the draft only. The API, the MCP address, the web app and the connectors all read the published version.
• The order for a change to reach callers is always: edit, Save, then Republish.
• One exception applies at once without saving or publishing: creating the first token or revoking the last one switches the token requirement of the live service. See Tokens and access.

FAQ

Where is the Save button?

Save appears at the top right of the service page as soon as something has changed. Without unsaved changes the same place shows Publish or Published.

Does saving change my live API?

No. Saving stores the draft; callers keep getting the published version. Click Republish in the Published menu to make saved changes live.

What exactly is saved when I click Save?

The workbook, the inputs, outputs and AI areas, the service settings, the AI definition and the app settings. Only the parts that changed are sent.

Why does the app say "Please save your changes before publishing"?

Publishing uses the saved state of the service. Click Save first, then Publish or Republish.

I closed the page without saving. Are my changes gone?

Yes, unsaved changes are dropped when you choose Leave without saving or confirm the browser's warning. The last saved state stays as it was.

Why does it say "No changes to save"?

The draft already matches what is stored, so there is nothing to send. If you expected a change, check that your edit was really applied in the workbook or the panel.

My save was refused because the workbook is too large. What now?

Each plan allows a certain workbook size, and a save that would go over it is refused. Make the workbook smaller or move to a larger plan; see File size limits.

As an agent, how do I know whether a user's change is live?

A change is live only after it was saved and the service was published again. A saved but not republished change exists in the draft only.