Invalid version range error in Get Changes action

[Bartek97]

Hi,

Recently I started getting an error in action "Get Changes": Invalid version range 

clientRequestId: be210efb-dbfa-4503-bf43-bedf8ee11873
serviceRequestId: be210efb-dbfa-4503-bf43-bedf8ee11873 

The flow is triggered when an item is modified in Share Point list. Sometimes I'm getting this error (for instance 5 times in a row) and a few minutes later the flow runs successfuly for the same item.

It happened only a few days ago, before it was working fine and there were no changes to the Share Point list or the flow itself.

The flow looks like this and the issue is in the second action at the very beginning:

Error:

Thank you in advance

[creativeopinion]

@Bartek97 I believe the error is indicating that whatever you have in the Since and Until fields are invalid.

Can you show what you currently have in the Get changes for an item or file (properties only) action?

For more flow troubleshooting tips—check out This YT Tutorial: 5 Power Automate Troubleshooting FAQs and Helpful Tips for Creating Better Flows

In this tutorial I cover:

✅ How to troubleshoot a false Condition action result

✅ How to get dynamic content when it isn’t selectable from the list of dynamic content

✅ How to troubleshoot an Apply to Each action that isn’t looping through

✅ How to troubleshoot a skipped Apply to Each action

✅ How to troubleshoot a Filter Query

✅ How to use a SharePoint yes/no column in a Filter Query

✅ How to use Compose actions to troubleshoot a Power Automate flow

✅ How to troubleshoot multiple emails being sent

✅ How to troubleshoot multiple Teams messages being sent

[Jiojio]

Hey, I have the same error, currently I have the default Trigger tokens that are given by the Power Automate. The flow was running fine till yesterday. But now the flow is being executed multiple times without even making any changes to the SharePoint list.

[creativeopinion]

@Jiojio are you using the New Designer or the Classic Designer?...

If you are using the the New Designer, I'd recommend switching to the Classic Designer for now as the New Designer still has a few bugs. 

[Jiojio]

I am using the classic designer.The error seems to be with the since and until part of the get changes for an item or file field.

[jenn3]

Having the same issue. It fails occasionally but mostly doesn't, and I can't seem to find any rhyme or reason for teh fails.

[IBennett]

I now also getting this error on flows that have been running successfully for years.

Has anyone figured out why?  Or a solution?  even rerunning it seems to fail.

One I have failing is currently at version 0.10.  there are other flow runs for 0.1-0.9 and >0.11.

I wonder if there is a conflict between recognising 0.10 as 0.1

Any patterns that you have noticed?