-
Notifications
You must be signed in to change notification settings - Fork 151
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.
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
Create a single log for a batch execution which contains a series of log entries for all the batches #693
Comments
I'm running into the same issue |
@stephenpstanley this sounds very similar to issue #499 that you opened last year - is this a duplicate? |
Ah yes, I think you are right. When I raised it I thought that I remembered something similar but I couldn't find it in the issues list. I expect it's because this is a completely different project at a VERY different scale where I'm getting hundreds of batch Apex executions which makes the noise factor much more significant How is your thinking progressing on a solution? Might there be an option to get transaction ID rather then the parent transactionID and set that for all subsequent batches? Feel free to merge or close as a duplicate |
@stephengoodcloud no worries, I'll close this as a duplicate & will keep #499 to track this. At the moment, I still don't have a solution designed for this, but I'm hoping to revisit it later this year. I don't plan to change the the behavior of when/how |
New Feature Summary
I'd like to be able to have a single log record created when a batch job is executed containing a series of log entry records , but it seems that the mechanism documented as below creates a new log record for the start, each execute and the finish, resulting in hundreds (or thousands) of log records when there are many batches to process
==== Code from the readme ======
public with sharing class BatchableLoggerExample implements Database.Batchable, Database.Stateful {
private String originalTransactionId;
}
The text was updated successfully, but these errors were encountered: