Skip to main content

​
Authentication

​
”Not authenticated” error

Run pragma auth login to authenticate.

​
Token expired

Re-authenticate with pragma auth login.

​
Resources

​
Resource stuck in PENDING

Check if dependencies are in ready state:
If dependencies are listed, verify each one is ready. A resource with unready dependencies waits in pending until all dependencies are satisfied. If all dependencies are ready but the resource is still pending, re-apply it:

​
Resource stuck in PROCESSING

Resources in processing state are being handled by a provider. If a resource stays in this state longer than expected:
  1. Wait — Pragmatiks automatically detects stuck resources and retries them
  2. Check the dead letter queue — If retries are exhausted, the resource moves to failed:
  1. Re-apply — Force a new processing attempt:

​
Resource failed

Check the error message:
Fix the configuration and re-apply:

​
Resource not updating after dependency change

If a resource isn’t updating after its dependency changed, check the resolved_config:
Compare config (your declaration) with resolved_config (what the provider received). If resolved_config still shows old values, the dependency change may not have propagated yet — verify the dependency is in ready state.

​
Deletion not working

If a resource won’t delete:
  • Resource in failed state — Failed resources can still be deleted. Check for errors:
  • Resource in processing state — Wait for the current operation to complete, then try deleting again.
  • Delete from YAML — Use the file-based delete to remove multiple resources:

​
File Uploads

​
File upload fails

When using @path syntax for pragma/file resources:
  • Verify the file exists at the specified path (relative to the YAML file’s directory)
  • Ensure content_type is specified in the config — it’s required for file uploads
  • Check the file size is within the platform’s limits

​
File resource stuck in FAILED

If a pragma/file resource fails with “File content not uploaded”:
  1. The file resource was created but the file content wasn’t uploaded yet
  2. Re-apply the resource with the @path syntax to trigger the upload:

​
Dead Letter Events

​
Events piling up

Check dead letter queue:
Investigate individual events:

​
Bulk cleanup

Clear all dead letter events for a provider after resolving the issues:

​
Provider Development

​
”Could not detect provider package”

Run commands from the provider directory, or specify --package:

​
Getting Help

Contact support at support@pragmatiks.io.