Skip to main content
Log inGet free account

Troubleshoot

Review solutions to common Quicksilver troubleshooting scenarios.

Discuss in Slack
Edit this page on GitHub Report an issue with this doc

This section provides solutions to common Quicksilver debugging and troubleshooting scenarios.

Debugging via Terminus

Use the Terminus commands in the sections below to debug Quicksilver.

Stream New Workflows to the Console

Run terminus workflow:watch <site> to follow your site's WebOps activity.

Explore Previous Workflows

List and show previous workflows and their corresponding Quicksilver operations with the following commands:

  • terminus workflow:list <site>
  • terminus workflow:info:logs <site> --id=<workflow>
  • terminus workflow:info:operations <site> --id=<workflow>
  • terminus workflow:info:status <site> --id=<workflow>

Troubleshooting

MultiDev Creation Hook Does Not Run When Expected

Quicksilver hooks for the create_cloud_development_environment workflow will not be detected when creating a Multidev environment if the pantheon.yml file does not exist on the Dev environment. As a workaround:

  1. Commit the pantheon.yml file on Dev.

  2. Create your Multidev environment after the commit is pushed.

Deploying Configuration Changes or Quicksilver Hooks to Multidev

Configuration changes are not be detected when creating a Multidev environment if a pantheon.yml file does not exist on the Dev environment. As a workaround:

  1. Make some modification the pantheon.yml file.

  2. Re-commit to the Multidev environment. You will then receive a notice indicating configuration changes have been detected and applied to the Multidev environment:

    remote:
remote: PANTHEON NOTICE:
remote:
remote: Changes to `pantheon.yml` detected.
remote:
remote: Successfully applied `pantheon.yml` to the 'new-feature' environment.
remote:
remote:

Autopilot VRT Hook Does Not Run When Expected

Quicksilver hooks are not detected due to timing issues with Multidev creation for some Autopilot users. If your Quicksilver autopilot_vrt scripts are not running:

  1. Verify that your scripts are defined in the Dev environment.

  2. Delete your Autopilot Multidev from the Dashboard.

  3. Delete the Autopilot branch of the Multidev.

  4. Create the Autopilot Multidev again in the Dashboard. Your scripts should start running after the visual regression tests complete.

More Resources