Forum Discussion
Teams Shifts: DataSource.NotFound: OData: Request failed (404): Error en el servidor remoto: (404)
Estoy haciendo una conexión por OData Feed Microsoft graph para traer la infomación de timeOffRequests de la aplicación de shifts de teams. De repente dejo de funcionar de un día para otro arrojando el siguiente error:
DataSource.NotFound: OData: Request failed (404): Error en el servidor remoto: (404) No se encontró. ()
Detalles:
DataSourceKind=OData
DataSourcePath=https://graph.microsoft.com/beta/teams('teamid')/schedule/timeOffRequests
Url=https://graph.microsoft.com/beta/teams('teamid')/schedule/timeOffRequests?$skiptoken={"token":"+RID:~Ak9YAI0TSgCLLSUAAAAwAw==%23RT:1%23TRC:500%23RTD:D7+ZURmwzNgffoqqBqTxBMNPD+8ZP/lllg==%23ISV:2%23IEO:65551%23QCF:8%23FPP:AghHAAAAwAwAAJkAAADADAAARwAAAMAMAAAKAAaXnqYCwAIIABBIAAAAwAwAAAIAJ5RJAAAAwAwAACIAh4CFhiEAQQBRl22AC4ACwEABCAB9gW2BM5GpgtCCwQBAAUoAAADADAAACgA1jYCArIkcgB2BSwAAAMAMAAAkAL+HMoGNhV6JX4gBwAAVEoBEgbEACQCBAaAAk4Bwj+OEUQFAREwAAADADAAAIgA7hQGAyJTshDCAt4I5hO2GEg5AEJEANQAgiAABACQBEAAETQAAAMAMAADEANOGh4BBAQAF8IDXgBqAqYSBhAqAeIEggHMBAYAQAAABEoASACIAAARDAKAECAAQABEAQAEkgAfAAQEAAESCAAAAKAIAAEoBBoAQwIBngDmAiYD5gALAogiAEPIAIBGAACSAEwQAgUBEIEKEgPKA/oDdgE6AAsCElEgCHIBRAYACN4ALgI2AEIEFgDEAJAAXgIGACYBZgCOBioakgSgAoAQBAAIiEAEAUAAEAgEEAJMAAIQAiCSEhIFYgESAnoALgDEBAApOAAAAwAwAAOgAEIBJgUQIIAEAJACAkCA1AAQCBAAEAEAIAEAhACgAEgAABQEArYF+gBSAAcAAgSaAoQCgAMuAAIAfgGSAU4BGgXuDQIACAQAFAQCbgATAEBAAAEASAgBhABACyoGFAACCAEBQBQBQACAmgM2ABIDQgCEAiCAQgZaC74ANgFCAooB2gAeA34Axg+qBSoDlgBSAIQCAQBIAQAEBAFEAQBF
la información carga de manera previa en power query
pero al intentar cerrar y cargar arroja el error
ya he intendado borrar los permisos, borrar la fila con error pero no funciona y en los turnos de teams todo esta perfecto
1 Reply
A few steps to isolate this:
1. Test the exact same URL (with a fresh $skiptoken removed, just the base request) directly in Graph Explorer (developer.microsoft.com/graph/graph-explorer) using the same account/permissions. If it also 404s there, it confirms this is a Graph API change, not a Power Query/OData connector issue.
2. Check the Microsoft Graph changelog (learn.microsoft.com/graph/changelog) around the date it stopped working for any entries related to "schedule" or "shifts".
3. If Graph Explorer confirms the beta path is gone or changed, try the v1.0 equivalent instead of beta - Microsoft has been migrating several Teams Shifts/Schedule endpoints from beta to v1.0, and the URL structure can differ slightly (e.g. permission scopes or required headers like MS-APP-ACTS-AS may be needed in v1.0 that weren't required in beta).
4. Also double check the "teamid" and any $skiptoken value aren't stale/expired - if this came from a previous paged response that's since expired, replaying that exact token could also produce a 404 rather than a more typical "expired token" error.
If Graph Explorer works fine with the same call, then it's worth sharing your M code (the OData.Feed call itself) since the issue would more likely be in how headers/tokens are being passed from Power Query.
