[Kelly]

Hi, materdknights. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, Katarina. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, trevellyan. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, Jen. This is just a note to let you know that as much as we were trying to, we didn’t get a your issue resolved in time for our maintenance release this time around. 🙁

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, fusionstudio. Unfortunately, we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, zengirl. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, Jonah. Thanks again for letting us know about this one.

This is just a note to let you know that we didn’t get a chance to look at it for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

It’s always great to hear from you!

[Kelly]

Hi, millcreekpark. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, Kristy. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, Kevin. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, folks. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, John. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, oceanfilm. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, reneeyoxon. This is just a note to let you know that we didn’t get a chance to look at your issue for our maintenance release this time around.

While it’s possible we may have inadvertently fixed it in addressing another issue and welcome your feedback to confirm or deny this once you’ve updated, we want to set your expectations.

Rest assured getting this resolved is still a priority for us. We look forward to addressing this as soon as we’ve got bandwidth/resources to allow it.

Thanks for being part of the TEC community!

[Kelly]

Hi, folks. This is just a quick shout to let you know that we will be rolling out a fix for this issue in our next maintenance release, due out later this week.

If for some reason, you’re still experiencing the issue, please let us know in a new forum thread.

Thanks so much for your patience!

[Author]

Posts