Page MenuHomePhabricator

Wikidata Bridge error
Open, Needs TriagePublic8 Estimated Story Points


The error happened on:
Item title: Q1219675
Property: P571
Debug information:

        "type": "INITIALIZATION_ERROR",
        "info": {
            "errors": [
                    "code": "badtoken",
                    "info": "⧼badtoken⧽",
                    "docref": "See for API usage. Subscribe to the mediawiki-api-announce mailing list at <> for notice of API deprecations and breaking changes."
            "name": "Error",
            "message": "badtoken",
            "stack": "_r@\nmwApiRejectionToError@\nmightThrow@\n"

Acceptance Criteria

  • If the error lies in mediawiki or in bridge, the bug is fixed. Otherwise, explain the origin of the error on the ticket and ping Lydia.

Related Objects

Event Timeline

Restricted Application added a project: Wikidata. · View Herald TranscriptMon, Feb 8, 3:13 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Restricted Application added a project: wdwb-tech-focus. · View Herald TranscriptMon, Feb 8, 4:05 PM
Lydia_Pintscher added a subscriber: Lydia_Pintscher.

Thank you for the report.

darthmon_wmde updated the task description. (Show Details)
darthmon_wmde updated the task description. (Show Details)


As far as I can tell, this error was returned from the API action wbgetentities upon initialising.
Data Bridge recognises errors from that API action if they are related to the Entity missing, anything else is thrown as the API returns it. This is the case here, judging by the stack.

One thing I can't explain is why the error message says "bad token". We are not sending any tokens for this action. It simply requests the info and the claims about the Entity.
An edit token is send when saving changes, with API action wbeditentity, but that action couldn't have happened since the Data Bridge error message is INITIALIZATION_ERROR.
I double checked the code and INITIALIZATION_ERROR is not thrown anywhere else but upon starting Bridge when Entity info and claims are required.

For further investigation into this mystery we're going to need more info, for example a timestamp can be useful to check the error on Kibana or Logstash (not sure where the board is).

Thank you!

For the timing: I would guess close to when this ticket was filed.