Best Of

@MichelleWatkins_GPP Hi Michelle!

I'm a bit confused regarding where external collaborators fall.

We are rolling out a SIS (school information system) and plan to have a "project lead" at each of the schools we are working with (they are external to our organization and do not share email domains).
The idea is that we create the general layout for the project plan (we are owners of each sheet) and the school project lead adapts dates and makes minor adjustments (edits the sheet, may or may not share with other people in the school). Also, the school project lead should be updating progress on tasks (ideally on the sheet itself).

The project is estimated to last 12-18 months.

Would this require us to purchase licenses for each school project lead (external collaborators), or can they edit the sheets for free?

Thanks!

How do I view sheet summary fields in Table View? I have a large sheet that only works properly in Table View, but I don't see how to get to the sheet summary page and how to add sheet-level attachments. If I switch back to Grid View to access those, the sheet won't save because it has too many cells. I'm in a Catch-22…

I've tried to raise a support query, but can only find a route through the AI chat bot. However this has failed to raise a support call on my behalf. The first time it said it logged something but i never got email confirmation nor is anything logged in my cases. I tried again but "something went wrong" so it asked me to try again, which I did, but this time it failed once more and suggested I send an email to support@smartsheet.com. I sent the query as suggested, only to receive an automated email telling me my case is closed and that the email address is no longer in use.

The chat bot couldn't direct me to a support form, nor can I see any way to log a case through the website, and I've just been redirected in circles back to the bot which doesn't work

This is a terrible backward step compared to the support we used to enjoy from Smartsheet. I can't post my sepecifc case on a public board. Please could someone get back to me with a route to resolve my billing query.

My company, too is having the same issue. Looking forward to a resolution soon!

My company is receiving this error as well. Hopefully this bug will be fixed soon.

This started happening to my team yesterday as well!

I’m hoping someone can help me understand a strange issue I’ve run into.

I have a workflow that sends a single Update Request when the date in a row matches today’s date. This automation has been working correctly for a long time—each contact would receive one email on the day it triggers.

However, recently the workflow has started sending two identical emails at the exact same time to the same contact, even though:

• Nothing has changed in my workflow
• The contact cell contains only one contact
• The conditions still evaluate the same
• The trigger is still set to run once daily at 5:00 AM

I’m including screenshots of my trigger, conditions, and message settings (images attached in my post).
Here’s what the workflow does:

Trigger:

• When a date is reached
• Runs daily Monday–Thursday at 5:00 AM

Conditions:

• “Is Today” is checked
• “Date” is not blank
• “SBO Item” contains “#”

Action:

• Send Update Request to the contact in the “Foreman Contact” column
• Only one contact is stored in that cell
• Message is customized, using specific fields only

Despite all this, each row that qualifies is now sending two identical Update Requests instead of one.

Has anyone seen this behavior before, or know what might cause a workflow to start sending duplicates?
Is this possibly a bug, or is there something I should double‑check in my sheet or automation settings?

Thanks in advance for any help—really appreciate it!

Hi everyone,

Thanks for reporting this issue with the Timeline widget.

Our Engineering team is currently investigating this behavior. While we don't have a specific ETA just yet, please know that we are working to resolve this as soon as possible.

We really appreciate your patience, and I will update this thread as soon as a fix is confirmed.

Cheers,
Isaac.