I'm getting this error message - [428] We're sorry, but your save failed because someone else tried to save this project at the same time. Please try to save again.
For context I'm creating a task using custom api module see attached image. I have iterating value which is getting added as a suffix to the task name. For example if I have 3 values, three task(with value suffix) should be created but two task are getting created and I'm getting this runtime error.
suggestion needed to fix the issue.
Custom api module output
iterator value
Topics help categorize Community content and increase your ability to discover relevant content.
Views
Replies
Total Likes
Hi @DestPr
As with your last question I can't tell because I don't see the module configuration nor the flow of the modules.
If you repeatedly get this same error please provide more info so we can troubleshoot.
Views
Replies
Total Likes
Hi @Sven-iX,
Below is my full workflow -
The Steps are 1>trigger is related to changes in task as language field get updated or newly added.
2> The read records module are there to get some data about Project and Custom form.
3>The iterator is there to pass the value as a suffix while creating task.
4> The main module is create product combination module used to create task. here is the configuration of it.
The problem is as above that when I'm adding 3 values I should get 3 tasks but 2 tasks are getting created or sometimes just one task is generated, followed by that error which i mentioned.
Views
Replies
Total Likes
Hi @DestPr
Thank you for that!
Sadly I have more questions
So if I understand correctly the first iterator loops over the list of suffixes from the tools module?
I can't tell what #4 is - Create Product Combination?
Some more questions & comments:
Views
Replies
Total Likes
I think description is pretty clear, action was not completed because there was parallel action happening on the project. I would just re-try, e.g. with error handler.
If I get this type of error in incomplete executions I usually don't have issues with re-running them successfully
Views
Replies
Total Likes
This can happen if you're updating a series of tasks on the same project. From what I can tell, sometimes Fusion runs faster than Workfront and so if Workfront is still trying to save the previous commit when Fusion calls the next, this error can happen. My suggestion would be to either add an automatic retry with a couple second pause, or to leverage the bulk update command and update all of the tasks at one time.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies
Views
Likes
Replies