Skip to content

Metenox (SystemName - Name) Broken for single corp #28

Closed

Description

@issue-migrator

📦 Migrated from GitLab
Original Issue: GL-#0124
Author: @Viaharo
Created At: 2025-11-12T18:26:07.802Z
State at Migration: opened
Labels: support


For some reason new metenox come through into the structures module as
SystemName - (no Data) causing child integrations to break.

Testing of ESI confirms name comes through on the structures by ID and also by corp structure esi list.

image

Only the one corp in question comes through as (no data) for the name.
Others work just fine.

image

image

Activity

  1. issue-migrator commented on Jul 13, 2026

    @issue-migrator
    Author

    📦 Migrated Comment | Author: @Viaharo | Date: 2025-11-13T05:19:37.193Z | Original

    when transferred to another corp for testing.

    image

    the names come through, and structure services for the corp before with out the names coming through, come back online and show green again under structures / owners.

    image

    if i transfer even one of the metenox drills back to the corp with the issue, structure services go down and the name of the metenox in auth goes back to (no data)

  2. ErikKalkoken commented on Sep 9, 2026

    @ErikKalkoken
    Contributor

    Fixed by #40

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    source: gitlabThis issue was migrated from GitLabsupportThis label was migrated from GitLab

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions