simPRO API Forum

This is an intermittent problem, but often when I PATCH a job to change the Status, the job's status does not get changed.

Here's an example:

sending the PATCH

GET the job:
As you can see, the job Status is still 75.

I can prove the rest of the PATCH is working by changing the Name:

The Status still hasn't changed:

Please can you investigate this issue?

Hi wildhart,
Thank you for the examples and for reporting this.

I was able to reproduce the behaviour you describe. It wasn't consistent so some statuses were updated and others not. I will do some more investigations on this issue so we can raise a ticket for this.

Regards

Hi @Sindre,

How are you getting on with this? Do you have a timeframe for getting this fixed?

It's a fairly fundamental bug and is blocking us from releasing new features to our users, and possibly causing your other API users issues they may not be aware of...

Hi,
We are not able to give a specific time frame for when a fix is being released. We are continually prioritising our work based on what will give the greatest benefit to our API users.

Regards

Hi,

We are also experiencing the same issue when updating quotes where the status updates are ignored with we get back the 204 response. The worst part is we get a webhook event back which causes our software to revert the status internally. Overall this is causing the users affected by this issue a lot of problems and frustration.

Any fix or workaround would be appreciated.

Thanks

Hi wildhart,
The status codes in simPRO are ordered in a hierarchy in which they usually progress from top to bottom in the setup.

If you try to patch a job with a status to one with a lower status you can't do this unless the option "Ignore status priority" has been activated on the status code.

If you patch to a status code higher in the hierarchy you should have no problems.

The API is currently returning 204 even if a status code is not being updated which I understand is not expected behaviour for the user and we will look at this.

If you want me to give some examples and do some more tests please send me a private message with your build details.

Regards

Hi Sindre,

Thank you for the explanation. Now we know the rules, we can change the "Ignore status priority" on that status and it works.

Yes, I agree that the 204 response is not expected in this circumstance - it would be helpful if it responded with an error and a helpful message.