Skyvern incident
Workflow runs failing to start for runs using saved credentials
Resolved after 1 hour 4 minutes, affecting Skyvern Async Workers, on October 10, 2026.
Starting at approximately 4:45 PM PT (23:45 UTC) on October 9, workflow runs that use credentials saved in Skyvern's credential vault failed to start, with the error "Failed to initialize workflow run context." The cause was an expired authentication secret that Skyvern uses to access its credential storage. This was an issue on our side, and customers do not need to take any action. We replaced the secret and restarted the affected services at approximately 5:35 PM PT (00:35 UTC). New runs are now starting normally. Runs that failed to start during this window did not execute. Please re-run any affected runs during this period. We are monitoring and will post a final update once we confirm everything is stable.
Affected components
Update timeline
- monitoring Oct 10, 2026, 12:38 AM UTC
Starting at approximately 4:45 PM PT (23:45 UTC) on October 9, workflow runs that use credentials saved in Skyvern's credential vault failed to start, with the error "Failed to initialize workflow run context." The cause was an expired authentication secret that Skyvern uses to access its credential storage. This was an issue on our side, and customers do not need to take any action. We replaced the secret and restarted the affected services at approximately 5:35 PM PT (00:35 UTC). New runs are now starting normally. Runs that failed to start during this window did not execute. Please re-run any affected runs during this period. We are monitoring and will post a final update once we confirm everything is stable.
- resolved Oct 10, 2026, 01:43 AM UTC
Everything looks healthy. Incident has been resolved.
Your product runs on more than Skyvern
Add the vendors you depend on and get one message when any of them reports trouble. Free for 3 vendors, no card.
Amazon Web Services