Sequential processing turned off. Successfully run, but then it's trying to run it again and that's where the error occurs.

In settings, I checked Sequential processing. I deleted everything from the queue. I turned the scenario on (immediate) and triggered a request (issue) to run thorough. It ran the full scenario successfully, but then I got an error 15 seconds later and Fusion shut down the scenario. I believe the we...

I will take all the help I can get!I'm using a Watch Events trigger like you suggested. My scenario runs completely through and does all the "things", but it will only run manually (Run Once), and something is being left unprocessed in the queue. I'm trying to figure out what exactly is being left b...

This worked! I have a few more issues to work out, but this was by far the biggest hurdle. Many, many thanks to you!

I will definitely try this - thank you so much!

Hi all - still fairly new to Fusion, but here's what I'm trying to do: When a user approves an Issue, I'm using Fusion to auto-convert to a Project with a specific template applied. I'd like to pull the ID of the user that approved the issue and assign them as the project owner at project conversion...

This helped me SO much!! The Portfolio field has been a thorn in my side for about 5 years. This solution will solve a major problem for us. Thank you 1000x!!

This is how we decided to do it out of the gate 5 years ago. The intake form just kept getting bigger and bigger and more complex with calculated fields and display logic. Our users have been complaining about having to fill out "too many fields" like forever. So now, we're trying to take a step bac...

Hello! We currently have one very long, very complex intake form that we're in the process of reevaluating. I've heard that if there is not a need to report on specific fields/data collected, it really doesn't belong in Workfront. I'm hoping to hear about some best practices and use cases regarding ...

Hi Randy, your response in this string is super helpful. I'm wondering if you could expand a bit on #3 - Avoid multi-part questions; "yes, no, other. Then a second field for the "other". We have a TON of these "other" fields in our intake form.1. What is your reasoning behind not using them?2. What ...