Error Explanation? APIModel INTERNAL does not support field duration (OpTask) | Community
Skip to main content
quarkmage
Level 3
July 9, 2024
Solved

Error Explanation? APIModel INTERNAL does not support field duration (OpTask)

  • July 9, 2024
  • 5 replies
  • 1418 views

Can anyone explain this error that seems to occur when a user is modifying advanced assignments.:

 

Error
APIModel INTERNAL does not support field duration
(OpTask)

 

thanks.

 

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by skyehansen

Support let me know this is now resolved, and I am no longer receiving the error in my instance.

5 replies

Kurt_Jones
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 9, 2024

I would actually suggest you input a support ticket, seems the system may be struggling reaching the API environment.

If my response answered your question, please mark it answered, so others can find the answer
skyehansen
Community Advisor and Adobe Champion
July 10, 2024

I've already logged a case for this here:

https://experienceleague.adobe.com/en/docs/workfront-known-issues/issues/new-workfront-experience/wf-current/wf-issues-error-when-making-assignment

 

If I recall correctly, the workaround is that you edit the issue/request, and add it that way, rather than using Advanced assignments in the upper right corner of the issue landing page.

Level 2
July 10, 2024

Just ran into this as well, did you end up submitting a ticket?

quarkmage
quarkmageAuthor
Level 3
July 10, 2024

thank for looking into this and engaging this request.

I am not too familiar with this issue, but does not seem to be an issue for other users also accessing and changing advanced assignments.  Please reach out if more info needed to support the ticket.

 

skyehansen
Community Advisor and Adobe Champion
skyehansenCommunity Advisor and Adobe ChampionAccepted solution
July 16, 2024

Support let me know this is now resolved, and I am no longer receiving the error in my instance.

quarkmage
quarkmageAuthor
Level 3
July 18, 2024

We are no longer experiencing this error on our instance.

Thanks for the support.