Possible API issue

(Dylan Caudill) #22

Thanks, @Nathan_Wilkes.

I’ve passed this along to the team and they’re investigating this issue. I appreciate the information!

(Nathan Wilkes) #23

@dylan, another occurrence just now at 19:28 or so Pacific. I presume this gives you enough to work on, but let me know if any further information would be helpful.

Thanks.

(Dylan Caudill) #24

Thanks @Nathan_Wilkes. I checked in with the team and they’re currently investigating. At this time we don’t need any further information but I’ll be sure to keep you updated here when I receive additional feedback from the team.

(Dylan Caudill) #25

Hi @Nathan_Wilkes,

Thanks for your patience here. The team has confirmed that they’ve been able to reproduce and that they’ve passed a ticket over to our development team to resolve things. I can’t provide any specific timeframes, but I’ll be sure to keep you updated here.

Thanks,
Dylan

(Nathan Wilkes) #26

Wonderful; thanks for the update @dylan .