Skip to content

Conversation

@labkey-jeckels
Copy link
Contributor

Rationale

Admins and users will find it easier if we track NextFlow invocations on a per-job basis, instead of a globally across all NextFlow jobs.

Changes

  • Create a nextflow schema and table table to track invocation counts
  • Change logging to more clearly differentiate between the initial queuing and subsequent execution-based messages

long invocationCount = INVOCATION_SEQUENCE.next();
INVOCATION_SEQUENCE.sync();
NextFlowPipelineJob.LOG.info("Starting to execute NextFlow: {}", getJob().getJsonJobInfo(invocationCount));
NextFlowManager.get().incrementInvocationCount(getJob());
Copy link
Contributor

Choose a reason for hiding this comment

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

should this be in try catch?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I don't think that would add anything. We need to increment the number whether the execution succeeds or not. I need the new value for the logging call on the next line, so I can't really delay it either.

@labkey-jeckels labkey-jeckels merged commit f060b04 into release24.11-SNAPSHOT Mar 19, 2025
3 of 4 checks passed
@labkey-jeckels labkey-jeckels deleted the 24.11_fb_nextflowInvocationCount branch March 19, 2025 03:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants