We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Describe the bug A clear and concise description of what the bug is. Screenshots are great!
In this case, the Test 3 sensor is showing as updating 39 minutes ago.
However,
It appears to have more recent data when zooming into the last 2 days in the APP UI
It also seems to be showing recent data in the dashboard...
To Reproduce Steps to reproduce the behavior:
UNKNOWN
Expected behavior A clear and concise description of what you expected to happen.
Smartphone (please complete the following information):
Additional context Add any other context about the problem here.
The text was updated successfully, but these errors were encountered:
Maybe fixed by #271 ?
Sorry, something went wrong.
needs retesting - @marthakeezy, are you able to check for us? @DhanyaHerath thanks for the advice!
Hey @mark-prins, yep I saw that happen before! All documented on Adam's Trello Board here.
Even right now when I checked CCA, the last record is showing to be from 3 days ago even though the actual records appear in omSupply
Thanks @marthakeezy!
No branches or pull requests
Describe the bug
A clear and concise description of what the bug is. Screenshots are great!
In this case, the Test 3 sensor is showing as updating 39 minutes ago.
However,
It appears to have more recent data when zooming into the last 2 days in the APP UI
It also seems to be showing recent data in the dashboard...
To Reproduce
Steps to reproduce the behavior:
UNKNOWN
Expected behavior
A clear and concise description of what you expected to happen.
Smartphone (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: