Dirty save - #BLOCKED/Invalid Value issue when using integration until manually save the sheet

Hello everyone,

We’re facing a critical issue in one of our Reports.

We use integration and it adds values to the sheets. The corrected values don't seem to auto-save.

Formulas in sheets first show #BLOCKED/Invalid Value, then if we refresh the sheet - it updates to the correct numbers. The save button is active even though we do not make any changes (integration supposedly works at midnight).

Because of this, the report shows #BLOCKED as well until we manually refresh the sheets.

It never happened before when we used integration.

SmartSheet support does not seem to have an answer or solution.

Is there a way to force auto-save after formula refresh or API updates?
SmartSheet team – can this be escalated?

Thank you in advance

Find more posts tagged with

Sheets

Reports

Accepted answers

All comments

Kate Orendochka

Hi Team,

We’re facing the same issue. After API integration or SCC Global Updates, some formulas briefly show #BLOCKED until the sheet is manually opened and saved. When I open the sheet, certain formula columns briefly show #BLOCKED and then display the correct values without any manual changes. The Save button becomes active even without edits.

I’ve been working with SCC Global Updates and similar formulas for 3+ years without seeing this problem before. It also happens across two different clients and solutions, so it’s not environment-specific.

Is there a workaround or a way to force auto-save after API or Global Update changes?

Paul Newcome

I have had this issue before, and support was able to correct it on the back-end. I would suggest reaching back out to support and escalating.

anastasiia.lemish

@SmartSheet Management could you assist please? We would appreciate if you could fix all Project Billing sheets in PM Offices on your end.

We need these sheets working as soon as it’s critical for the client experience, and the accounting team will get reports with errors and missing data if the issue isn’t resolved.

Paul Newcome has mentioned that this issue was already fixed, so maybe you could apply the same fix or run the API “dirty save” code on your end?

We are very much looking for your support here.

Thank you

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, sort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.