Problems with a job that rebuilds indexes
You should rebuild index which it deadlocked on, and rebuild any other indexes which not did not occur afterwards- if whole job failed and stopped.
Hopefully you are rebuilding indexes, during less busy times, say nighttime or after hours. If you have no choice, and have a continuously busy system,
Please Rebuild with Online option,

ALTER INDEX ALL ON [dbo].[Test] REBUILD WITH (ONLINE = ON);

Additionally, I would only rebuild indexes which require it.  Hallengren website has an option to reorganize indexes say with 5% Fragmentation, and rebuild for 30% Fragmentation. I don't think Windows SQL Server Maintenance has this option yet.

EXECUTE dbo.IndexOptimize
@Databases = 'USER_DATABASES',
@FragmentationLow = NULL,
@FragmentationMedium = 'INDEX_REORGANIZE,INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@FragmentationHigh = 'INDEX_REBUILD_ONLINE,INDEX_REBUILD_OFFLINE',
@FragmentationLevel1 = 5,
@FragmentationLevel2 = 30,
@UpdateStatistics = 'ALL',
@OnlyModifiedStatistics = 'Y'



Check when the deadlock occurred, and how the long the total job duration lasted. If those points meet, then the job stopped at the deadlock. If the job duration lasted longer than deadlock, more indexes were rebuilt.