-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Workspace - Does not detect the expense category after turning on and off in the policy #44377
Comments
Triggered auto assignment to @adelekennedy ( |
We think this issue might be related to the #collect project. |
@adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick! |
@adelekennedy 6 days overdue. This is scarier than being forced to listen to Vogon poetry! |
@adelekennedy Now this issue is 8 days overdue. Are you sure this should be a Daily? Feel free to change it! |
@adelekennedy 12 days overdue now... This issue's end is nigh! |
I somehow missed this one 😮💨 |
i can't reproduce this one - and we're on such a later version that I think we're safe to close for now |
If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!
Version Number: 9.1.0.8
Reproducible in staging?: Y
Reproducible in production?: Y
Found when validating PR : #43869
Email or phone of affected tester (no customers): applausetester+az090524@applause.expensifail.com
Logs: https://stackoverflow.com/c/expensify/questions/4856
Issue reported by: Applause-Internal team
Action Performed:
Prerequsites:
Steps:
Expected Result:
The error of the Category should not longer be presented
Actual Result:
The error is still present even though the categories are already active
Workaround:
Unknown
Platforms:
Which of our officially supported platforms is this issue occurring on?
Screenshots/Videos
Bug6523195_1719247492052.Video_de_WhatsApp_2024-06-24_a_las_11.21.11_222a31f2.mp4
Bug6523195_1719247492066.prod.mp4
View all open jobs on GitHub
The text was updated successfully, but these errors were encountered: