**Problem statement & User Impact**
Abstract Wikipedia does not provide the same level of detail when errors occur in article previews as Wikifunctions.
As a result, users cannot easily understand why a specific call is failing or where the issue originates. Instead, they have to manually reproduce the error in Wikifunctions to access more detailed information.
**Example**
Steps to replicate the issue:
On Abstract Wikipedia:
- Go to https://abstract.wikipedia.org/wiki/Q30
- Change the preview language to Spanish
- What happens?
```
Error message result: //Wikifunctions returned a failed response: No matching lexeme for item in language//
```
On Wikifunctions:
- Open the replicated function call [[ https://www.wikifunctions.org/view/en/Z26039?call=%7B%22Z1K1%22%3A%22Z7%22%2C%22Z7K1%22%3A%22Z26039%22%2C%22Z26039K1%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q30%22%7D%2C%22Z26039K2%22%3A%7B%22Z1K1%22%3A%22Z6091%22%2C%22Z6091K1%22%3A%22Q3624078%22%7D%2C%22Z26039K3%22%3A%22Z1003%22%7D | here ]]
- Click on details
- What happens?
```
Error message includes more details: //Errors
No matching lexeme for item in language (Wikidata item QID: "Q3624078", connecting properties PIDs: "P5137", language codes: "es")//
```
**Suggested Scope**
Enable contributors to access the more detailed error information already available in Wikifunctions when errors occur in Abstract Wikipedia.
**Edge cases**
While the example above returns a relatively short error message, we need to consider what should happen when error messages are long - keeping in mind that they can also be user generated.
**Approach**
Approach is open (and we will potentially have to review scope as well) and will be explored with engineering and design before committing to a specific solution (e.g. displaying more detail in the Abstract Wikipedia interface or enabling easy navigation to detailed error on Wikifunctions, etc).
**Additional context**
Previous example raised in this task:
If you look at a page without valid lexemes (e.g. Q11750 in Spanish), it does not indicate which item the lexemes were invalid for. Users should be able to understand why the specific call is failing and where the issue occurs.
//Note: Was not able to reproduce this example//