Expand my Community achievements bar.

SOLVED

Complete Task ending up in Drafts folder

Avatar

Former Community Member

Has anyone ever experienced a completed task showing up in a draft folder rather than being processed by the next activity in the process?

I have a user who says she completed 2 tasks, yet the tasks never completed (either in ADMINUI or in my logs) and somehow ended up in her Drafts folder.  I have not seen this behavior first hand, so am not sure the story is 100% accurate, but the Save as Draft and Complete Task buttons are on opposite sides of the screen.  Not sure how she could get them confused.

1 Accepted Solution

Avatar

Correct answer by
Former Community Member

When a task (form) is submitted, first the data is saved and then task is completed.  If anything goes wrong, such as a submit process failure, and the task isn't completed, because the data was saved and the task is still owned by that user, it will appear in their drafts.

But, there should have been an error msg to both the user and the logs.  Have them check their logs for any indication of a problem.

Jon

View solution in original post

2 Replies

Avatar

Correct answer by
Former Community Member

When a task (form) is submitted, first the data is saved and then task is completed.  If anything goes wrong, such as a submit process failure, and the task isn't completed, because the data was saved and the task is still owned by that user, it will appear in their drafts.

But, there should have been an error msg to both the user and the logs.  Have them check their logs for any indication of a problem.

Jon

Avatar

Former Community Member

Ok.  Thanks for that info.

In this specific instance, I don't see any error information in the LC log (LCServer1.out) that indicates there was a problem during the submission of her task.  Is there some place else I should check?

The following has evaluated to null or missing: ==> liqladmin("SELECT id, value FROM metrics WHERE id = 'net_accepted_solutions' and user.id = '${acceptedAnswer.author.id}'").data.items [in template "analytics-container" at line 83, column 41] ---- Tip: It's the step after the last dot that caused this error, not those before it. ---- Tip: If the failing expression is known to be legally refer to something that's sometimes null or missing, either specify a default value like myOptionalVar!myDefault, or use <#if myOptionalVar??>when-present<#else>when-missing. (These only cover the last step of the expression; to cover the whole expression, use parenthesis: (myOptionalVar.foo)!myDefault, (myOptionalVar.foo)?? ---- ---- FTL stack trace ("~" means nesting-related): - Failed at: #assign answerAuthorNetSolutions = li... [in template "analytics-container" at line 83, column 5] ----