Migrated to Queueable with limit error handling, added Flow Action #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
handles output with ContentDistribution, tests run but real world times out with Apex limit
- added email notification - added target CustomObject for file link - (added secondary package.xml for my testing)
need to update package to remove
unified process, added custom exception and heap check to try to avoid/warn about memory issues
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was hoping to use this in a Flow, so I added a simple Invocable to the package, but then I found that there was just too thin a Limits margin to run Zippex the normal way, so I migrated that call into a Queueable. I still end up hitting a lot of Apex Limits, so I've got some error handling in there to try to catch it, but I figured maybe someone can use this and/or improve on it!