A trashed instance is still activated and also in cost status.
You can reproduce this by stopping an on-demand job and archiving it by clicking the delete command, Don't delete immediately instead drop it into the trash. Yet, the system still thinks this archive is active and charges money.
I think the archived job is dead which releasing all GPU resources, and should not cost money.
Picture about the transaction.
Instance in trash
Trashed Instance still in cost
Recommend resolving methods:
Can we regard the trashed job as the right way to release all resources, stop the on-demand jobs, and could not cause any costs?
Explain the issue
A trashed instance is still activated and also in cost status.
You can reproduce this by stopping an on-demand job and archiving it by clicking the delete command, Don't delete immediately instead drop it into the trash. Yet, the system still thinks this archive is active and charges money.
I think the archived job is dead which releasing all GPU resources, and should not cost money.
Picture about the transaction.
Instance in trash
Trashed Instance still in cost
Recommend resolving methods:
Can we regard the trashed job as the right way to release all resources, stop the on-demand jobs, and could not cause any costs?