Lookups on Sharepoint Task get workflow into Suspended state.

All replies

  • How are you looking up for the task? I mean which activities you are using for Looking up task, getting task properties? Once the workflow is in suspended state, you should get a correlation id in the status that you can use to find details in the ULS log file. Also you can debug the problem on workflow side by using different types of logs:

    Sohel Rana

    Wednesday, June 05, 2013 1:09 AM
  • This is the Suspend state info I recieve.

    It comes when I do a Lookup against a Task

    Data Source-- WorkFlowTask --Created by ---Login Name--Id-- TaskId

    RequestorId: c7ecea27-1ac4-87ee-0000-000000000000. Details: An unhandled exception occurred during the execution of the workflow instance. Exception details: System.FormatException: Input string was not in a correct format.   at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)   at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)   at Microsoft.Activities.Expressions.ParseNumber`1.Execute(CodeActivityContext context)   at System.Activities.CodeActivity`1.InternalExecute(ActivityInstance instance, ActivityExecutor executor, BookmarkManager bookmarkManager)   at System.Activities.Runtime.ActivityExecutor.ExecuteActivityWorkItem.ExecuteBody(ActivityExecutor executor, BookmarkManager bookmarkManager, Location resultLocation)

    Can you see anything obvious?


    • Edited by kohler49 Saturday, June 08, 2013 9:24 PM
    Saturday, June 08, 2013 9:20 PM
  • Your workflow has some activity which expects or returns a numerical parameter.
    However the activity gets a parameter of type string.

    I have no idea, which activity is that, but I would recommend to find it and to change your parameter type from number (I think it is decimal) to string at least temporary to be able to execute the workflow.
    After that you can investigate what is string value and why it cannot be parsed to Decimal.

    Damir Dobric

    Sunday, June 09, 2013 4:24 PM
  • Hi,

    The way you can debug the issue is to write in Workflow History. Try to write something in Workflow History after every possible activity and then find out which activity is the one you have problem. I usually use workflow History in SharePoint 2013 workflow to track workflow progress.

    Sohel Rana

    Monday, June 10, 2013 12:33 AM
  • I had this same error when my workflow was using the Workflow Task list that comes with the Publishing feature. Created a new task list for the workflow and the suspending went away
    Monday, December 05, 2016 9:32 PM