# moving tasks to new workflows seems fragile

**URL:** <https://forum.certara.com/t/moving-tasks-to-new-workflows-seems-fragile/2358>\
**Category:** Phoenix WNL basics\
**Created:** [February 3, 2012, 7:41pm UTC](https://forum.certara.com/t/moving-tasks-to-new-workflows-seems-fragile/2358 "2012-02-03T19:41:18Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![fgibbons](https://avatars.discourse-cdn.com/v4/letter/f/ba8739/32.png) [@fgibbons](https://forum.certara.com/u/fgibbons)\
**Post date:** [February 3, 2012, 7:41pm UTC](https://forum.certara.com/t/moving-tasks-to-new-workflows-seems-fragile/2358/1 "2012-02-03T19:41:18Z")

</div>

I’m having a lot of trouble when I move tasks into sub-workflows. Connections with datasets seem to get lost, not always, but it sure feels like it’s about 60% of the time. What’s the best place to report this kind of thing? Do I email ‘support’, post it here, or both. I’m asking because it’s not necessarily “broken” - I mean, I can go right in, reconnect the dataset, and carryon, and the connection doesn’t break (unless I move it again). but it’s quite frustrating, and obviously it discourages building large workflows. Thanks -Frank

---

<div class="post-metadata">

**Author:** ![SimonDavis](https://avatars.discourse-cdn.com/v4/letter/s/d9b06d/32.png) [@SimonDavis](https://forum.certara.com/u/SimonDavis)\
**Post date:** [February 3, 2012, 8:09pm UTC](https://forum.certara.com/t/moving-tasks-to-new-workflows-seems-fragile/2358/2 "2012-02-03T20:09:18Z")

</div>

Hi Frank, That shouldn’t happen so it should be reported as a bug to support with an example project if possible. What version are you seeing this in? simon