A group of Microsoft Products and technologies used for sharing and managing content, knowledge, and applications.
The flow issues come from two different causes: how the items are being retrieved, and a data-type mismatch in an expression.
- Items stopping at ID 100
- This is typically caused by how the SharePoint items are being retrieved (for example, a default page size/top count, or a filter/order that only returns part of the list), not by the SharePoint view.
- In the flow run history, open a failed/successful run and inspect the output of the action that gets items from SharePoint. Confirm how many items are actually being returned and whether any filter or Top Count is applied.
- If pagination or limits are configured in that action, increase the threshold or enable pagination so that all 122 items are returned.
- Error “The template language function 'less' expects two parameter of matching types. The function was invoked with values of type 'Null' and 'String' that do not match.”
- This means the expression using
less()is comparing two values of different types. For some list items, the value being compared isnull(for example, an empty date column), while the other is a string. - To fix this, adjust the expression so both parameters are of the same type and handle nulls explicitly. For example:
- Use a condition to check
@not(equals(<yourField>, null))before callingless(). - Or convert both values to the same type (for example, both to numbers or both to dates) before comparison.
- Use a condition to check
- Use the flow run history:
- Go to My flows.
- Open the flow and select a failed run in the 28‑day run history.
- Open the failed step (the action where
less()is used) and review the Inputs and Outputs to see which field is null for those specific items. - Update the flow to guard against null values or to ensure the column is always populated before comparison.
After making these changes, run the flow again and monitor the run history to confirm that all items beyond ID 100 are processed and that the less() expression no longer fails for items with empty values.
References: