-
-
Notifications
You must be signed in to change notification settings - Fork 204
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
Save date when transition ran in document infodoc #9012
Comments
@1yuv @binokaryg @garethbowen |
Including the date seems like a no brainer! Maybe it could use a better name... "timestamp" isn't very descriptive. What about "execution_date" or something? |
Thanks @dianabarsan, I can't draw a picture how will this help with #9011 ? Will there be another PR that will re-run transition based on newly introduced |
Most transitions don't run more than once, @1yuv , the intention for this is to add more information into when the transition ran, to know for certain that it had run before or after another event (for example, before or after an SMS was generated). |
Thanks for the feedback, I changed it to |
Oof, yeah, |
What feature do you want to improve?
When a transition runs over a document, we store some metadata about this in the infodoc. It ends up looking like:
The information that we store is:
Describe the improvement you'd like
While debugging an issue where a field, that was supposed to be added by a transition, was missing from a generated sms message, there was no way of knowing when the transition ran, specifically whether it ran before or after the SMS message had been generated.
I'm suggesting we add an additional field to infodoc transition entries to store the date when the transition edited the document.
Describe alternatives you've considered
Leave it as it is.
Additional context
Having this information would definitively exclude the delayed sentinel scenario as an explanation for issues like https://github.com/medic/config-gandaki/issues/38
related issue #9011
The text was updated successfully, but these errors were encountered: