Skip to main content

Troubleshooting

An application does not output any logs.ā€‹

Make sure that you run your application with the correct debug levels.

Refer to the debugging topic for more information.

An application works correctly on the local machine but does not run on the cloud.ā€‹

Check the application's config.cloud.js configuration file. If your application does not run on the cloud, you may need to update this file after you changed the application's structure or updated the application to a new version of the reSolve framework.

Make sure that your read model projections are compatible with PLV8.

In reSolve Cloud, when you use the @resolve-js/readmodel-postgresql read model adapter, read model projection code is built as PLV8 code bundles to be executed on the database server side. PLV8 imposes the following restrictions on the projection implementation:

  • No runtime imports are allowed:

    // The code below is not supported by PLV8
    const myModule = await import('my-module')

  • No imports that run native code are allowed, including NodeJS inbuilt modules:

    // The code below is not supported by PLV8
    import fs from 'fs'

If your read model projections do not meet these requirements, they are built to be executed by Node JS at the cost of performance. In this case, the following warning is logged:

PLV8 procedure execution for the "${readModelName}" read model's projection failed. Trying to degrade to non-plv8 mode.
Reason: Native and runtime require dependencies are prohibited in PLV8.

How to view deployment errors?ā€‹

Use the describe command of the reSolve Cloud CLI. This command outputs the last error that occurred during the application's deployment.

resolve-cloud describe <deploymentId>