have seen this behavior many times in multiple orgs (logs do exist in the dev console though). Just waiting for SF to figure it out and fix it. Since one cannot report anything without being directed to the dev forums (they should send people here) they may not be aware although I highly doubt they have not run into it themselves.
In my case, opening the dev console and unchecking "Show my current logs only" allowed me to view existing logs. Although I cannot say for sure if they were all there since I could not see what was in the UI version...
Just in case it is helpful, you can also directly query for the Debug logs yourself using ApexLog. It's accessible in both the Partner API and the Tooling API. You would typically filter the ApexLog records by
Once you have the ID of the log you want you can then download it with:
One way as a workaround, assuming you're working with Apex code, is to:
- Write a test case for exactly what you are trying to test
Turn on Replay Debuggerusing SFDX Extension for VS Code
- Run your test case from VS Code
Get Apex Debug Logswith SFDX Extension.
I see my test case debug log in the Dev Console and the list returned from
Get Apex Debug Logs even if I don't see the log that I should've seen from trying it through the UI. I know it's not pretty but depending on requirements, it may be better than waiting until they magically start showing up again.