Enable the new calculation engine

The new calculation engine uses a modern JavaScript runtime for calculation fields. Enable it for each workspace where you want to use it. Existing workspaces continue to use the legacy calculation engine until you enable the new engine.

Use the Calculation fields migration guide to identify and update calculations that are incompatible with the new engine.

Why use the new calculation engine?

The new calculation engine provides faster calculation and workflow execution, support for modern JavaScript syntax and features, clearer error messages and stack traces, and a more secure runtime environment.

The legacy calculation engine is available only as a temporary fallback. Update your calculations and enable the new engine as early as possible, because future calculation-engine improvements are available only on the new engine.

Before you start

Keep the following in mind before you enable the new calculation engine:

• Workspace admins can enable the engine for one workspace at a time.
• Organization admins can enable the engine for multiple workspaces from Organization Settings.
• Workspace and app admins can override the calculation engine for a specific app.
• The legacy engine remains available as a temporary fallback.
• Existing calculations can display errors if they are not compatible with the new engine.

Enable the engine for one workspace

Workspace admins can enable the new calculation engine from workspace settings.

1. Open the workspace where you want to enable the new calculation engine.
2. Go to Workspace Settings.
3. Scroll to Calculation settings.
4. Enable the new calculation engine.
5. Save the setting if prompted.

The workspace now uses the new calculation engine unless an app has its own calculation-engine setting.

Enable the engine for multiple workspaces

Organization admins can enable the new calculation engine from the workspace list.

1. Go to Organization Settings > Workspaces.
2. Review the workspaces in your organization.
3. Select the calculation engine checkbox for each workspace where you want to enable the new engine.

To enable the new calculation engine for all workspaces, select Toggle Calculations for All.

The Calculation Errors column shows whether enabled workspaces have calculation errors. You can enable the engine for private workspaces that you are not a member of, but you can view errors only for workspaces that you can access.

Override the engine for an app

Use an app-level override to test the new engine in one app or to temporarily return one app to the legacy engine.

1. Open the workspace that contains the app.
2. Open the app that you want to configure.
3. Go to App Settings > Advanced.
4. Choose the calculation engine for the app.
5. Save the setting if prompted.

The app uses the selected engine. Other apps continue to use the workspace setting unless they have their own override.

Troubleshoot calculation errors

After enabling the new engine, review calculation errors and update incompatible calculation fields.

1. Open the workspace where the new engine is enabled.
2. Go to Manage Apps.
3. Review the apps in the workspace.
4. Select an app's error count to filter the list and view its calculation errors.
5. Update the incompatible calculation fields. See the Calculation fields migration guide for compatibility guidance.
6. Select Clear Errors after you fix the calculations.

An error count can include repeated failures from the same calculation field. Identify the underlying fields before you estimate the amount of work required. Clearing errors removes the existing error records and lets you monitor new errors after your updates.

Troubleshoot errors as an organization admin

Organization admins can monitor calculation errors from Organization Settings > Workspaces.

1. Review the workspaces where the new calculation engine is enabled.
2. Check the Calculation Errors column.
3. Open the errors page for a workspace that has errors.
4. In the selected workspace, review and troubleshoot the errors in Manage Apps.

You can troubleshoot only workspaces that you can access. Contact the workspace admins when a private workspace has errors that you cannot view.

Return to the legacy engine

If a calculation is incompatible with the new engine, you can temporarily return the workspace or only the affected app to the legacy engine.

1. To return a workspace, go to Workspace Settings > Calculation settings and select the legacy calculation engine.
2. To return an app, go to App Settings > Advanced and select the legacy calculation engine.
3. Save the setting if prompted.

Use the legacy engine only while you update incompatible calculations. Enable the new engine again after you resolve the errors.

Recommended rollout

For most workspaces, test the new calculation engine in stages to reduce the risk of workflow disruption:

1. Start with one representative workspace or app.
2. Review calculation errors in Manage Apps.
3. Update incompatible calculations and clear the error records.
4. Monitor for new errors as calculations run.
5. Repeat the process for the remaining workspaces.

Use app-level testing when you need more targeted control. Enable the new engine for one app, resolve its calculation errors, then enable the engine at the workspace level when the key apps are compatible. Use the organization-level workspace list to monitor adoption and calculation errors across your organization.

Frequently asked questions

Will all workspaces automatically use the new calculation engine?

No. Existing workspaces continue to use the legacy calculation engine until a workspace or organization admin enables the new engine.

Can I enable the new calculation engine for only one workspace?

Yes. A workspace admin can enable the new engine in Workspace Settings for that workspace.

Can organization admins enable the engine for multiple workspaces?

Yes. Organization admins can enable the engine for individual workspaces or all workspaces from Organization Settings > Workspaces.

Can organization admins enable the engine for private workspaces?

Yes. Organization admins can enable the engine for private workspaces that they are not members of. They cannot view calculation-error details for workspaces that they cannot access.

What should I do if calculations show errors after I enable the new engine?

Go to Manage Apps in the affected workspace. Select an app's error count to filter the list and review its errors. Use the Calculation fields migration guide to resolve compatibility issues, then select Clear Errors and monitor for new errors.

What does a calculation error count mean?

An error count shows how many calculation errors occurred in an app or workspace. A single incompatible calculation field can create repeated errors across multiple items, so the count does not necessarily equal the number of fields that you need to update.

Why should I clear errors after updating calculations?

Clearing errors removes historical error records and creates a clean baseline. New errors appear again if the updated calculations continue to fail.

Can I return to the legacy calculation engine?

Yes. You can temporarily return an entire workspace or an individual app to the legacy engine while you update incompatible calculation fields.

Can I enable the new calculation engine for only one app?

Yes. Workspace and app admins can choose an engine for a specific app in App Settings > Advanced. This lets you test the new engine in one app before you enable it for the workspace.

What happens when an app uses a different engine than its workspace?

The app-level setting overrides the workspace setting for that app. Other apps continue to use the workspace setting unless they have their own override.

When should I use an app-level override?

Use an app-level override when you need to test one app or keep an affected app on the legacy engine while you resolve compatibility issues.

How long is the legacy calculation engine available?

The legacy engine is available for a limited time. Podio has not announced an end date for legacy-engine support and will provide advance notice before retiring it. Do not rely on the legacy engine as a long-term solution.