Issue with Uploading Source Entries in Dev Environment

[saubhagya14]

Describe the issue

Hi Team,

I am facing an issue that works fine on my local machine but not in the dev environment. Could there be a gateway blocker or any environment-specific issue?

The problem is with uploading source entries using the add operation on an existing component. Locally, it works as expected, but in the dev environment, although I receive a success response, the newly added entries are not reflected in Weblate.

I already tried

• I've read and searched the documentation.
• I've searched for similar filed issues in this repository.

Steps to reproduce the behavior

1. Create Component

• Component creation was successful.
• Initially, the component had two keys.

2. Upload Source File (Adding Another Key)

• I uploaded a source file with an additional key.

3. Local Machine Behavior

• Received response: notFound=0, skipped=2, accepted=1, total=3, result=true, count=3

4. Dev Environment Behavior

• Received response: notFound=0, skipped=0, accepted=3, total=3, result=true, count=3
• The new key did not reflect in Weblate, even though the response indicates success.

Expected behavior

No response

Screenshots

No response

Exception traceback

How do you run Weblate?

No response

Weblate versions

No response

Weblate deploy checks

Additional context

No response

[nijel]

There must be some difference between "dev" and "local machine" environments or configurations. Maybe the component is configured differently?

[saubhagya14]

No, everything is the same. Even for testing, if I block the flow for some time, the dev changes will reflect in the Weblate UI.

Note : As per my analysis, if the component is created successfully in the API response, an internal task runs to check whether the component was configured successfully or not. In case it is not configured, when I try to upload a source file using the add method to add new entries, the addition does not work. However, the replace method works fine, which may indicate a bug in Weblate.

[nijel]

If everything were the same, the behavior would be the same as well.

Weblate does create the component in the background. Maybe you are accessing it too early before the processing is done on the dev environment and the changes you make are overwritten by the actual processing.