Test Interface Error 121052: Invalid JSON Format — No Logs Recorded

[hamaboualeg]

Hi team,

I'm encountering a persistent issue when using the test interface for Cloud Functions. When I run a test, I consistently receive the following error:

pgsql
Copy
Edit
121052: Invalid JSON format
However, there are no corresponding logs in the system — it appears as if the function is not invoked at all. This makes debugging impossible, as I can't determine whether the error lies in my input, the test tool itself, or the function runtime.

Steps to reproduce:

Go to the Cloud Function test interface.

Input test JSON (well-formed JSON confirmed via external validator).

Click "Test."

Receive error 121052: Invalid JSON format.

Check logs — no entries are created.

Expected behavior:

If the JSON truly is invalid, I expect a clear message pointing to the exact issue (e.g. syntax or structure).

If the function is not invoked, I would like to understand why — and have logs or errors that reflect this.

Ideally, the test tool should validate JSON before submission and prevent sending malformed data.

[hamaboualeg]

Update:
I was able to resolve the issue. The root cause wasn't the JSON itself, but rather the server region selected in the test environment.

If you're encountering the same "121052: Invalid JSON format" error with no logs, try this:

🔧 Fix:
In the Cloud Function interface settings (under "Règlage" or configuration), change the server region from Germany to another location such as Singapore or China.

After switching the server, the same JSON input that previously failed started working correctly, and the function was properly invoked with logs appearing as expected.

It seems the issue is specific to certain regional configurations and not related to the input format. Hopefully this helps others facing the same confusing behavior.