Skip to content

Fix "The field value for ExceptionMessage__c is too long" exception for long flow error messages #828

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
jongpie merged 2 commits into from
Jan 14, 2025
Merged

Fix "The field value for ExceptionMessage__c is too long" exception for long flow error messages #828

jongpie merged 2 commits into from
Jan 14, 2025

Conversation

@jamessimone
Copy link
Collaborator

@jamessimone jamessimone commented Jan 13, 2025

@jamessimone jamessimone requested a review from jongpie as a code owner January 13, 2025 20:26
@jamessimone jamessimone temporarily deployed to Advanced Scratch Org January 13, 2025 20:32 — with GitHub Actions Inactive
@jamessimone jamessimone temporarily deployed to Event Monitoring Scratch Org January 13, 2025 20:32 — with GitHub Actions Inactive
@jamessimone jamessimone temporarily deployed to Platform Cache Scratch Org January 13, 2025 20:48 — with GitHub Actions Inactive
@jamessimone jamessimone temporarily deployed to OmniStudio Scratch Org January 13, 2025 20:48 — with GitHub Actions Inactive
@jamessimone jamessimone temporarily deployed to Experience Cloud Scratch Org January 13, 2025 20:51 — with GitHub Actions Inactive
@codecov
Copy link

codecov bot commented Jan 14, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.46%. Comparing base (daf14e9) to head (8b07c8f).

Additional details and impacted files 
@@            Coverage Diff             @@
##             main     #828      +/-   ##
==========================================
+ Coverage   85.97%   91.46%   +5.49%     
==========================================
  Files          17       58      +41     
  Lines        1319     6269    +4950     
  Branches      200      200              
==========================================
+ Hits         1134     5734    +4600     
- Misses        165      515     +350     
  Partials       20       20
Flag Coverage Δ
Apex 92.92% <100.00%> (?)
LWC 85.97% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

jongpie
jongpie approved these changes Jan 14, 2025
View reviewed changes
Copy link
Owner

@jongpie jongpie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jamessimone this looks great! I'm merging it now + creating release notes for it, thanks again for working on this 🎉

@jongpie jongpie merged commit d897e3f into main Jan 14, 2025
1 check passed
@jongpie jongpie deleted the bugfix/flow-logger-exception-message-truncation branch January 14, 2025 02:58
@jongpie jongpie added Type: Bug Something isn't working Logging Source: Flow Items related to using Nebula Logger within Flow Layer: Logger Engine Items related to the core logging engine labels Jan 14, 2025
@jamessimone
Copy link
Collaborator Author

jamessimone commented Jan 14, 2025

Awesome, happy to help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@jongpie jongpie jongpie approved these changes

Assignees

No one assigned

Labels

Layer: Logger Engine Items related to the core logging engine Logging Source: Flow Items related to using Nebula Logger within Flow Type: Bug Something isn't working

Projects

None yet

Milestone

Version 4.16.0: Spring '25 Release

Development

Successfully merging this pull request may close these issues.

Flow logging actions don't properly truncate some string fields

3 participants

@jamessimone @jongpie @actions-user