Keon Amini

Is this something we can solve by using a JSON-Schema for these request payloads?

@mindlesscloud can you try again? I think my latest merged PR will have fixed this. I just setup an env and got a 428 as expected, and after running migrations...

Okay, I'll expand the scope of #2940 and push a fix there since it's already in progress. @e2corporation Does config-ui consume any other endpoints that would return a certain error...

And as an idea, probably for another ticket, it might be a good idea to standardize the Backend->Frontend error-message format across all APIs to use some sort of JSON on...

@e2corporation, what do you think about this output?  For multiple invalid tokens: 

@e2corporation #2984 has been merged. Now the backend returns a JSON like the one I mentioned [above](https://github.com/apache/incubator-devlake/issues/3031#issuecomment-1242545195), so if there's any UI side changes that are needed they can be...

Is this happening after merging #2907? Also, this is a good chance to use the ENABLE_STACKTRACE flag in the .env file to see some stacktraces in the logs. Set it...

Ah, actually I think it may be because of the migration error code. It's supposed to come back as 428, but it's 500. #2940 is fixing that.

At the meantime, as a workaround, just hit the backend with CURL to change the migration status.

I take it back about being related to 2940. That error message wouldn't relate to migrations.