Smartsheet Product Feedback & Ideas

Smartsheet Product Feedback & Ideas

Help shape the future of Smartsheet! Share your feature wishlist and improvement requests here.

Sign in to submit new ideas and vote
Get Started

Increase Bridge Run Log Entry Limit / Update Error Prompt

If an individual Bridge run log entry exceeds 4mb of data, you'll see the error message “Run logs aren’t loading right now…” with a suggestion to check your internet connection.

The error prompt is incorrect, and unhelpful.

  1. Improve the usage of Bridge by increasing the data load limit to align against the limitations within Smartsheet.
  2. Improve the error prompt by updating it with the actual issue. BRIDGE has data limitations, which are easily exceeded.


Tags:
11
11 votes

Idea Submitted · Last Updated

Comments

  • ✭✭✭

    Just upvoted this since I've encountered it too many times now.

    Its sporadic and occurs at the most crucial moment when you are trying to debug something. The surprising thing is that the same set of workflows sometimes produce excessive logs and (most of the other times) they are ok.

  • I also just upvoted this. Does it eventually clear itself? I'm trying to debug a workflow and I'm basically stuck.

  • @Genevieve P. do you know if is there a fix for this. I can't access the run logs several workflows I'm working on. I receive the same error. Is there a way someone at Smartsheet can clear my logs?

  • Hi @Randy Naganuma

    There currently is no way to bypass the 4mb limit at present, other than splitting up the workflow into multiple, smaller workflows.

    The workflows will continue to run successfully, but the details within the Run Log will not be viewable. Thanks for adding your vote to this Idea!

    Cheers,
    Genevieve

    Need more information? 👀 | Help and Learning Center

    こんにちは (Konnichiwa), Hallo, Hola, Bonjour, Olá, Ciao!👋 | Global Discussions

  • Thanks @Genevieve P.

    For anyone that runs into this issue but still needs to troubleshoot and see your run log because you're still developing the workflow (like I am), I was able to move the workflow to another workspace and continue developing it. This treats it as a new workflow and the run log is blank.

    One thing to take note of, when you move a workflow to another workspace, the triggers don't transfer over so you'll want to create those first so it's easier to associate the trigger to the workflow that's being copied over.

Trending Ideas