Skip to content

Updated expense workflow timeout to 12 mins #88

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

Merged
merged 2 commits into from
Feb 6, 2025

Conversation

vishwa-uber
Copy link
Contributor

@vishwa-uber vishwa-uber commented Feb 6, 2025

What changed?

Updated StartToCloseTimeouts for the workflow to 12 mins

Why the change?

Workflow was timing out even before I approve or reject the expense report as the ExecutionStartToCloseTimeout was set to 1 min. There are three activities that have a cumulative scheduleToCloseTimeout of 12 mins but we were setting ExecutionStartToCloseTimeout for the whole workflow to just 1 min.

Screenshot 2025-02-05 at 5 56 14 PM

How did you test it?

Unit tested the timeout error

Potential risks

No risks

@vishwa-uber vishwa-uber changed the title Recalibrating expense workflow timeout to 12 mins Updated expense workflow timeout to 12 mins Feb 6, 2025
Comment on lines 56 to 57
// s.env.OnActivity(waitForDecisionActivity, mock.Anything, mock.Anything).Return("APPROVED", nil).Once()
// s.env.OnActivity(paymentActivity, mock.Anything, mock.Anything).Return(nil).Once()
Copy link
Member

Choose a reason for hiding this comment

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

better to avoid checking in commented code.

@vishwa-uber vishwa-uber merged commit 6739dd6 into master Feb 6, 2025
2 checks passed
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