You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
If 'since' and 'until' parameters are just a few microseconds apart, the rendered schedule may be empty. If they match exactly, we get a rendered schedule as expected.
Explanation / How to reproduce:
We use 'get a schedule' to determine which person is working at a specific time and date. We wrote a function that takes the Team ID, and (optionally) the 'since' and 'until' parameters. If the user did not specify values for 'since' or 'until', we were getting the current datetime as ISO 8601 including microseconds... making TWO calls, one per parameter. The call failed sometimes but not others.
When we modified our function to get the current datetime ONCE, and then substituted in that one value when either parameter was not explicitly passed in, the functionality worked as expected.
The text was updated successfully, but these errors were encountered:
Summary:
If 'since' and 'until' parameters are just a few microseconds apart, the rendered schedule may be empty. If they match exactly, we get a rendered schedule as expected.
Explanation / How to reproduce:
We use 'get a schedule' to determine which person is working at a specific time and date. We wrote a function that takes the Team ID, and (optionally) the 'since' and 'until' parameters. If the user did not specify values for 'since' or 'until', we were getting the current datetime as ISO 8601 including microseconds... making TWO calls, one per parameter. The call failed sometimes but not others.
When we modified our function to get the current datetime ONCE, and then substituted in that one value when either parameter was not explicitly passed in, the functionality worked as expected.
The text was updated successfully, but these errors were encountered: