Project Cleanup DRC
Thought for 5 sec
A week and a half without a clear diagnosis or ETA is an excessive delay for a production-blocking issue. I cannot see Flux Support’s internal queue, so I can’t tell whether the ticket is unassigned, waiting on engineering, or stalled.
Send this escalation in the existing thread:
This issue has now blocked the project for approximately 10 days. I still have no confirmed diagnosis, assigned engineer, resolution timeline, or viable workaround. Please escalate this case to an engineering lead or support manager today and provide:
- The current case status and owner.
- Whether the virtual stitch-via failure has been reproduced.
- A target date for repair.
- A supported alternative, such as repairing the project data or providing a clean project copy that preserves the schematic and usable layout.
The board cannot proceed to production while these stale connectivity records remain. Please do not close the ticket as “needs routing,” because repeated routing attempts do not clear the affected airwires.
If the existing thread remains unanswered, resubmit it through Contact Support and reference the original ticket and project URL.
Thought for 5 sec
I can’t provide a legitimate ETA because I don’t have access to Flux engineering’s queue or the authority to schedule backend work. Any timeline I gave would be speculation.
Send this to support:
This project has been blocked for approximately 10 days, and I now need a concrete engineering timeline. Please provide:
- The assigned engineer or responsible team
- Whether the issue has been reproduced
- The current repair stage
- A target completion date
- A workaround or clean project migration plan if the backend repair cannot be completed within two business days
Please escalate this to a support manager or engineering lead. A general statement that the board “just needs routing” does not address the virtual stitch-via endpoints that cannot be selected, deleted, or satisfied by physical copper.
Use the existing ticket thread or Contact Support. Until they confirm action, we should avoid spending additional ACUs on repeated checks.
Ask for fix ETA
Escalate stale records
Check support reply
Waiting for input
