Assist is a platform where teams can build, host, and deploy internal AI software and agents in one place — giving companies a safe, controlled environment to standardize workflows and improve operations.

What are sandcastles?

Sandcastles are purpose-built internal apps created by non-technical teams on the Assist platform. They allow employees to build custom tools and workflows without engineering resources.

How much does Assist cost?

Assist uses pay-as-you-go pricing: provider costs + 5%, $0.17 per 1k tool calls, with no seat fees. Enterprise custom pricing is also available.

Do we need engineers to use Assist?

No. Assist is designed for non-technical teams to build and deploy AI tools. Engineers can use it too, but it doesn't require engineering resources to get started.

Troubleshooting

Common issues and solutions related to scheduled triggers and job runs.

No run appears at the scheduled time

The trigger may not be active. Ask the AI to list your scheduled tasks and confirm the trigger shows as active. If it was disabled, ask the AI to re-enable it.

The schedule or timezone may be incorrect. Verify the trigger's schedule configuration by listing your tasks. If the time or timezone is wrong, create a new trigger with the correct settings.

Give the system a short buffer. Runs may take a few moments to appear after the scheduled time. Refresh the Tasks page after a minute or two.

The run failed

Open the run details and check the execution log. Click the failed run in the Tasks list to see the error message and timestamped log entries. The error section shows what went wrong.

The agent's prompt may need adjustment. If the error relates to tool access or an unclear instruction, update the trigger by creating a new one with a refined prompt.

The agent may not have the required tools. Confirm that the agent assigned to the trigger has access to the tools needed for the task.

No Slack notification was received

Confirm both Slack connections are present. Scheduled trigger notifications require the workspace Slack integration and your personal Slack identity to both be connected.

Check the run status. Successful and partial runs are included in a periodic digest, not sent immediately. Only failed runs trigger an immediate notification.

The notification may still be in transit. If the run just completed, wait for the next digest window for success or partial notifications.

The trigger was created but the AI did not confirm the next run time

The trigger may have been created without a valid schedule configuration. List your scheduled tasks and check that the trigger has a next run time. If it does not, create a new trigger with explicit schedule details (hour, minute, timezone).

Rerun Task button is not responding

A rerun may already be in progress. The button shows "Rerunning..." while the request is being processed. Wait for the rerun to complete before trying again.

Check your network connection. If the button does not respond at all, refresh the page and try again.

Runs show "Partial" status

The agent completed the task but encountered issues with some steps. Open the execution log in the run details to see which steps succeeded and which had problems. You may need to adjust the trigger prompt or the agent's tool access to resolve the issue.

I want to change a trigger's schedule

Create a new trigger with the updated schedule, then disable the old one. Ask the AI to disable the existing trigger and create a new one with the corrected schedule. Triggers cannot be edited in place from the chat.

The Tasks page shows "No agent tasks yet"

No triggers have fired yet. If you just created a trigger, wait for the next scheduled run time. You can also use Rerun Task on an existing trigger to create a run immediately.

Still need help? Contact your workspace administrator.