As a
Wikidata user who is editing a newly created Property,

I want to
be able to add multiple statements (e.g., Wikidata property examples) to the new Property without encountering 500 errors or timeouts.

In order to
improve the experience of creating and editing Properties in Wikidata.

What problem are you trying to get solved?
Multiple editors have experienced frequent 500 errors and timeouts when attempting to add Statements to new Properties. Specifically, after successfully adding the first "Wikidata property example" statement, attempts to add a second statement result in the Property page becoming inaccessible for several hours.

Describe the impact that solving this problem will have on users:
Fixing this issue will prevent delays caused by inaccessible pages.

Describe the implications/cost of not fixing this bug:
If this issue is not resolved, it will slow users' contributions to Wikidata and lead to frustration.

List of steps to reproduce:

1. Create a new Property.
2. Add the first Statement, e.g. Wikidata property example (P1855) and save it successfully.
3. Attempt to add a second Statement.
4. The property page becomes inaccessible, resulting in a 500 error and timeout. It takes several hours before the page becomes accessible again.

Error Details:

If you report this error to the Wikimedia System Administrators, please include the details below.
Request from <ip redacted> via cp3072 cp3072, Varnish XID 344343058
Upstream caches: cp3072 int
Error: 500, Internal Server Error at Fri, 23 Aug 2024 13:46:36 GMT

Acceptance Criteria:

• Users should be able to add multiple statements to new Properties without encountering 500 errors or timeouts.
• The Property pages should remain accessible for further editing after each statement is added.

Previous discussion:
See discussion on Wikidata:Report a technical problem#Issues with adding statements to a new property.

Open Questions:

• Could this issue be related to recent system outages, and if so, how can we prevent this from happening in the future?
• Since this issue appears to be reported only for Item-type Properties, could there be specific differences between Item-type Properties and other types, such as External Edentifier Properties or String Properties, that might be contributing to the problem?