Power App Form Error: Submit Issue & Power Platform Solutions

You may run into power apps form fails when working with forms in Power Apps. These issues can block your progress and cause frustration. Most of the time, you can spot and fix the problem without needing advanced skills. Stay alert for common warning signs. If you follow simple steps, you will solve most problems quickly and keep your projects moving forward.

Key Takeaways

• Identify common causes of Power Apps form fails, such as data source issues and field configuration problems.
• Check your data connections regularly. Broken or missing connections can prevent forms from working.
• Ensure data types match between your form and data source. Mismatched types can lead to submission errors.
• Always fill in required fields. Leaving them empty will stop your form from saving.
• Use the OnFailure property to provide clear error messages. This helps users understand what went wrong.
• Utilize the Monitor tool to track errors during user sessions. It helps you find and fix issues quickly.
• Test your forms after each change. Small adjustments can prevent larger problems later.
• Follow a troubleshooting checklist to isolate and resolve issues effectively.

13 Surprising Facts About Power App Form Errors

• Many form failures are caused by subtle delegation limits: a query works in preview but fails in production when a data source returns more rows than delegation allows.
• Broken forms often trace back to schema changes in the connected data source (column rename, type change) rather than Power Apps logic itself.
• Form validation rules in Power Apps can conflict with SharePoint or Dataverse column-level validation, producing confusing, duplicate error messages.
• Missing permissions on a single column (like Person or Lookup) can cause an entire submit to fail even if the user has list-level edit rights.
• Complex default formulas with Lookup or Filter calls can silently return blank records and make required fields appear populated when they are not.
• Using unsupported data types (such as multi-value choice fields or certain complex JSON fields) often causes inconsistent behavior between studio, preview, and mobile clients.
• Network latency and timeouts produce transient submit errors that are indistinguishable from formula errors unless you inspect the connector traces.
• Power Apps error messages are often generic; enabling Monitor or checking the connector’s response reveals precise HTTP status codes and backend error details.
• Concurrent edits by multiple users lead to merge conflicts or optimistic concurrency errors, especially when using custom APIs or flows to update records.
• Custom components and component properties can introduce subtle typing mismatches (text vs number vs record) that cause runtime form failures only after publishing.
• Using JSON Patch or complex Patch operations without updating Related records or lookup IDs can create orphaned records and trigger integrity errors on submit.
• Client-side formatting (like DateTime locale formats) can cause validation failures when the backend expects a different ISO format, varying across browsers and devices.
• Simple fixes—repointing to the correct schema, updating delegation-aware queries, adding explicit error handling, and using Monitor—resolve the majority of form failures far faster than rebuilding the form from scratch.

Power Apps Form Fails: Main Causes

When you work with Power Apps forms, you may face several common issues that can stop your form from working as expected. Understanding these main causes helps you fix problems quickly and avoid future headaches.

Data Source Issues

Data sources are the backbone of your forms. If something goes wrong here, you will likely see an error or a failed submission.

Broken or Missing Connections

You must keep your data connections healthy. If a connection breaks or goes missing, your form cannot send or receive data. For example, if you use Excel as a data source, you need to format your data as a table. If you do not, Power Apps will not recognize the data, and you will see an error message. Sometimes, Power Automate flows become disconnected. You need to re-add these flows to restore functionality.

Tip: If you see a connection error, check your data source settings and reconnect if needed.

Data Type Mismatches

Data type mismatches happen when the data you enter does not match what the data source expects. For example, if a SharePoint list expects a date but you enter text, the form will fail to submit. You may also see issues with date-time fields or blank values. Power Apps cannot save null or blank values to some data sources unless you enable formula-level error management. Always check that your field types in Power Apps match those in your data source.

Field Configuration Problems

Field configuration problems are another leading cause of power apps form fails. Each field in your form must match the columns in your data source.

Required Fields Left Empty

If you leave a required field empty, your form will not save. Power Apps marks required fields based on your data source settings. For example, if a field is required in a SharePoint content type, it will also be required in your form. Removing a field from your form without making it optional in the data source can also cause an error. You should always check which fields are required before publishing your form.

• The Title field is often unnecessary and can be hidden or made non-required.
• Required fields in content types are automatically set as required in Power Apps forms.
• Removing fields without ensuring they are not required can prevent form saving.

Field Name Mismatches

Field name mismatches can cause confusion and errors. If you change a field name in your data source but do not update it in your form, Power Apps will not know where to send the data. This often happens with the “Title” field in SharePoint lists. If you change the Title field that is referenced by lookups, you must remove the lookups, change the field, and then recreate the lookups. Always keep your field names consistent.

Note: In Power Apps forms, fields correspond directly to columns in SharePoint lists. You can enable or disable fields as needed, but make sure the names match exactly.

Permission and Access Errors

Permission and access errors are a frequent cause of power apps form fails. If you do not have the right permissions, you cannot submit or edit data.

User Role Issues

You need the correct role to use a form. If you lack permission to update a SharePoint list, you will see an error message. These errors can be confusing and may look like data type or required field problems. Always check your permissions if you cannot submit a form.

Sharing Problems

Sharing problems can also block access. If you share an app but the user does not have access to the data source, they will see an error. Sometimes, newly shared apps take a few moments to become available. Wait a bit and try again if you cannot access a shared app right away.

Tip: Make sure everyone who needs to use the form has the right permissions in both Power Apps and the connected data sources.

By understanding these main causes, you can spot and fix most errors before they become bigger problems. This knowledge will help you keep your Power Apps forms running smoothly.

SubmitForm and Patch Issues

When you work with forms in power apps, you rely on submitform and Patch functions to send data to your data source. These functions help you update SharePoint lists or other connected sources. Sometimes, you see an error when you try to submit data. Understanding why submitform and Patch fail helps you fix problems faster.

SubmitForm Failures

Submitform is the main function for submitting form data. You may run into errors if your form is not set up correctly. Here are some common reasons:

• Field mapping issues can cause errors if your form fields do not match the columns in your data source.
• Missing required columns often trigger validation errors.
• Problems with attachments can block submitform from saving data.
• Complex types, like people or choice fields, require manual handling.
• Validation errors happen when your inputs do not meet rules, such as incorrect data types or empty required fields.

Unsaved Property Problems

You need to check the form’s valid property before using submitform. If you skip this step, you may send invalid data and see an error. Always confirm that your form is valid. Use the iferror function to catch errors and display helpful messages.

IfError(
    SubmitForm(Form1),
    Notify("There was an error submitting the form.", NotificationType.Error)
)

Tip: Use the iferror function to handle errors and give users clear feedback.

Gallery Source Changes

If you change the source of a gallery, submitform may fail. This happens when the form loses its connection to the correct record. You should update the form’s Item property to match the new gallery source. Use the iferror function to check for errors after making changes.

Patch Function Pitfalls

Patch gives you more control over data updates. You can target specific fields, but you must use the correct syntax. Errors often appear if you reference fields incorrectly or miss required columns.

• Syntax errors can occur if you forget to use the As operator or ThisRecord in complex formulas.
• Field reference mistakes happen when field names collide or you use the wrong scope.
• Ambiguities in formulas may lead to errors that are hard to spot.

Note: Always use the iferror function with Patch to catch errors and troubleshoot issues.

IfError(
    Patch(DataSource, ThisRecord, {Title: "New Title"}),
    Notify("Patch error detected.", NotificationType.Error)
)

Syntax Errors

You must check your formulas for syntax errors. Use the As operator or ThisRecord to clarify which field you mean, especially in functions like ForAll or Filter. The iferror function helps you find and fix errors quickly.

Field Reference Mistakes

Field reference mistakes can cause errors if you use the wrong field name or scope. Always double-check your references. If you see an error, use the iferror function to pinpoint the problem.

By following these steps and using the iferror function, you can handle errors and keep your forms working smoothly.

Power Apps Forms Error-Handling

When you build apps, you want to make sure users do not get stuck by an unexpected error. Power apps forms error-handling helps you manage these situations. You can use built-in tools to catch problems, display helpful error messages, and guide users to fix issues. Handling unexpected errors keeps your app reliable and easy to use.

OnFailure Property

The OnFailure property plays a key role in error handling. You can set actions that run when a form submission fails. This means you can notify users right away if something goes wrong. You help users understand the problem and what to do next. This approach improves the user experience and makes handling unexpected errors much easier.

Custom Error Messages

You should always provide clear error messages. When you use the OnFailure property, you can show a custom error notification message. This message tells users what happened and how to fix it. For example, you can use the Notify function to display a message if a required field is empty or if there is a data type mismatch. You can also log errors for later review.

Tip: Use Notify with OnFailure to give users instant feedback and reduce confusion.

Best practices for configuring the OnFailure property include:

• Implement a global exception strategy for consistent error handling.
• Use a three-tier framework: local try-catch, app-level exception handling, and a global handler.
• Log errors and send alerts to keep everyone informed.
• Standardize error messages for easy troubleshooting.
• Integrate monitoring tools for real-time alerts.

User Feedback

You want users to feel confident when using your app. Always give feedback when an unexpected error happens. Use Notify to show a friendly message. Tell users if they need to check a field or try again. If you handle errors well, users will trust your app more. You can also use IfError to catch problems and display helpful tips.

Using Monitor for Troubleshooting

The Monitor tool helps you track and fix errors in your app. You can see what happens during a user session and spot where things go wrong. Monitor shows you every function that runs and if it succeeds or fails. You can filter the list to show only failures, which makes finding unexpected errors faster.

Interpreting Error Codes

When you see an error code, you need to know what it means. Follow these steps to interpret error codes and track submission failures:

1. Open the error code lookup tool in your browser. Enter the code and submit it.
2. Read the message to learn why the error happened and what to do.
3. If you are an admin, use PowerShell to audit sign-in failures and see more details.
4. Use report filtering to focus on specific error codes.
5. Save your filtered report for future reference.

Tracking Submission Failures

Monitor lets you track every submission. You can see when an unexpected error stops a form from saving. This helps you fix problems before users get frustrated. Monitor also helps you improve app performance and deliver a better experience.

By using OnFailure, Notify, IfError, and Monitor, you can master power apps forms error-handling. You will handle unexpected errors, provide clear feedback, and keep your app running smoothly.

SharePoint Integration Problems

When you connect your forms to SharePoint, you may face unique challenges. These problems can block data submissions or cause unexpected errors. You need to understand how SharePoint list rules and environment changes affect your forms.

List Validation Rules

SharePoint lists often have built-in validation rules. These rules help keep your data clean and accurate. If your form does not follow these rules, you will see an error message and your submission will fail.

Data Not Passing Validation

You must validate your data before submitting it. SharePoint checks every field against its rules. If any field breaks a rule, the form will not save. For example, a field might require a certain format or a minimum number of characters. You can use the Valid property in your form to check if your data will pass validation.

Tip: Always check the Valid property before submitting your form. This step helps you catch mistakes early.

Here are some common problems you might see:

Validation rules protect your data. They make sure only correct information enters your SharePoint list. If your data does not match the rules, SharePoint will reject the submission.

Column Type Issues

Column types in SharePoint must match the data you send from your form. If you try to submit text to a number column, you will get an error. You should always check your column types in both SharePoint and your form. This step prevents many submission problems.

• Make sure your form fields match the SharePoint column types.
• Update your form if you change a column type in SharePoint.

Environment Differences

You may notice that your form works in one environment but not in another. This happens when you move forms between testing and production or after making updates.

Testing vs. Production

Testing and production environments can behave differently. You might test your form in a safe space, then move it to production for real users. Sometimes, settings or data in production do not match your test environment. This difference can cause errors that did not appear during testing.

• Always test your form in an environment that matches production as closely as possible.
• Check for missing columns, different validation rules, or permission changes.

Updates and Modifications

Changes to your SharePoint list can affect your form. If you add, remove, or change columns, your form might stop working. A well-structured SharePoint list helps your form run smoothly. Poor design can slow down your app or cause delegation warnings. Delegation means Power Apps can only process a limited number of records if the query is not supported. This limit can lead to incomplete data or missed records.

Note: Review your SharePoint list design before making big changes. Good planning keeps your forms reliable as your data grows.

By understanding these integration problems, you can avoid common errors and keep your forms working well with SharePoint.

Performance and Connectivity

You want your forms to load quickly and respond smoothly. Performance and connectivity problems can slow down your work and frustrate users. Let’s look at what causes these issues and how you can fix them.

Slow Form Loads

When your form takes too long to load, users may lose patience. Several factors can make your forms sluggish.

Large Data Sets

If you connect your form to a data source with more than 2,000 rows, you may notice slow scrolling and delays. Loading too much data at once puts stress on your app and can lead to performance drops. High CPU and DTU usage in the backend database can also slow things down. You can improve speed by:

• Loading only the data you need for the current task.
• Using filtered queries to limit the number of records.
• Selecting only the columns you need, not the entire table.
• Avoiding SaveData() and LoadData() for large or complex data.

Tip: Always use explicit column selection to reduce load times and keep your app fast.

Too Many Controls

Adding too many controls, such as text boxes, buttons, or images, can make your form slow. Each control adds to the processing time. Complex formulas and inefficient navigation also contribute to lag. Try these steps:

• Remove unnecessary controls from your form.
• Simplify your formulas and logic.
• Group related controls to make the form easier to manage.

A clean and simple design helps your form run faster and reduces the chance of an error.

Network and Flow Issues

Connectivity problems can stop your form from working. You may see an error if your app cannot reach the data source or if a flow fails.

Unstable Connections

Unstable internet or network connections can interrupt your work. If you suspect a connection problem, you can diagnose it by:

• Launching the Power Automate machine runtime application and signing in.
• Using the diagnostic tool to check cloud runtime connectivity.
• Reviewing the generated report for details about relay gateways.
• Configuring your firewall with the correct DNS names.
• Running manual tests like TCP ping to confirm network status.

Note: Reliable connections keep your forms running smoothly and prevent unexpected errors.

Power Automate Flow Failures

Sometimes, a Power Automate flow fails and stops your form from submitting data. You can troubleshoot by:

• Checking the flow’s run history for failed steps.
• Reviewing error messages to find out what went wrong.
• Making sure all connections in the flow are active and authorized.
• Avoiding the use of Power Automate to populate collections unless necessary, as this can slow down your app.

If you follow these steps, you can quickly find and fix the cause of the failure.

By understanding these performance and connectivity challenges, you can keep your power apps forms fast and reliable. Always monitor your app and address issues before they affect users.

Quick Fixes and Checklist

Step-by-Step Troubleshooting

You can solve many problems in Power Apps by following a clear troubleshooting process. Start with these steps to quickly find and fix common issues:

• Isolate changes: Undo recent edits and return to the last working version. Make one change at a time. This helps you spot the exact cause of the problem.
• Simplify the form: Remove extra controls or fields. A simple form is easier to test and less likely to have hidden errors.
• Start from scratch: Build a new form or app with the same data source. Compare the new version to your original. This can reveal configuration mistakes or missing settings.
• Check each layer: Look at the server, network, app, and device. Problems can happen at any layer. Test your app on a different device or network to see if the issue remains.
• Reproduce the issue: Try to make the error happen again. Consistent steps make it easier to find and fix the root cause.

Tip: Always test your form after each change. Small steps help you avoid repeating the same mistake.

Here is a quick checklist you can use:

When to Ask for Help

You can fix many issues on your own, but sometimes you need extra support. Ask for help if:

• You cannot find the cause after following the checklist.
• The error keeps happening even in a new app or form.
• You see permission or access problems that you cannot resolve.
• The issue affects many users or blocks important work.
• You need to change advanced settings or use custom code.

Note: Gather details before reaching out. Take screenshots, write down error messages, and list the steps you tried. This information helps support teams solve your problem faster.

By using this checklist, you can solve most Power Apps form issues quickly. You will know when to keep troubleshooting and when to ask for help.

You have learned the main causes of power apps form fails, such as data source issues, field configuration problems, and permission errors. You can fix most power apps form fails by following a simple checklist and using built-in tools.

• Review your forms regularly.
• Test each change before publishing.
• Give users clear feedback.

Tip: Apply best practices to keep your power apps forms reliable and easy to use.

Checklist: Power Apps Form Errors (power apps form fails and simple ways to fix them)

Use this checklist to identify and resolve common Power Apps form errors quickly.

• Confirm data source connectivity: Verify the SharePoint, Dataverse, SQL, or other connector is connected and the credentials/token are valid.
• Check delegation warnings: Review queries for non-delegable functions and limit data volume or apply delegable alternatives to prevent incomplete results.
• Validate field names and schema: Ensure form fields match the current schema (internal names, column types) of the connected data source.
• Inspect required fields and validation rules: Confirm required property, Regex, and custom validation formulas are correct and provide user-friendly error messages.
• Verify Patch/Submit formulas: Test SubmitForm, Patch, and UpdateIf logic for correct record references, defaults, and error handling (Use Errors() to capture issues).
• Check control properties and Default/Update values: Make sure Default, DefaultSelectedItems, and Update properties are set appropriately for forms and cards.
• Review permissions and security roles: Confirm the app user has proper read/write permissions in the data source and any environment-level roles (Dataverse, SharePoint permissions).
• Test on device and network conditions: Reproduce errors on different browsers, mobile devices, and network speeds; consider offline behavior and caching.
• Monitor formula performance: Simplify heavy formulas, avoid nested lookups in galleries/forms, and use collections or cached data where needed.
• Handle concurrency and locking: Implement version checks, use Patch with conditions, and handle conflicts when multiple users edit the same record.
• Check app version and component updates: Ensure the app and custom components are published, and users run the latest version; review component input/output mappings.
• Use diagnostics and logging: Enable Monitor, check App Checker, use Trace or custom logging to capture errors and stack traces for troubleshooting.

submission sharepoint list error message power fx form control

Why does my Power Apps form fail to submit to a SharePoint list?

Common causes are mismatched data types between form fields and SharePoint list columns, required fields left blank, or an invalid connector configuration. Check that each form control (text input, picker, boolean toggles) matches the corresponding SharePoint list column type and that the Submit button OnSelect uses SubmitForm or Patch correctly. Use Power Apps Monitor and review errors that occur to see the requested operation is invalid details. Also confirm permissions on the SharePoint site and connector security updates haven’t blocked the operation.

How can I debug an error occurs during form submission?

Start with Power Apps Monitor to capture backend calls, response codes, and API failures. Add error handling in the Edit form OnFailure and OnSuccess formulas (onsuccess / onfailure): use Notify to inform the user and set a variable for debugging. Inspect the Text property of any Text input controls, check the form’s DataSource, and review the error message returned by SharePoint or the connector. If you see “requested operation is invalid,” verify list columns and required lookup values.

What should I check when a Save button doesn’t save data?

Verify the Save button OnSelect property calls SubmitForm(FormName) or uses Patch with valid field mappings. Ensure the form control’s Mode is Edit or New, and the form’s Item is set correctly. Confirm required fields are populated and that list using SharePoint list columns expects the same names and data types. Use Power Apps Monitor to confirm the backend call is sent and Microsoft 365 / SharePoint connector returns success.

How do I match the SharePoint list column types with my canvas app fields?

Open the SharePoint list settings to view column types and compare them with your form fields. For choice and boolean (true or false) columns, use the corresponding Choice control or Toggle input control. For Person or Group, use People picker connectors. For lookup fields, ensure you supply the ID value. If types don’t match, the submit will likely fail; adjust the property of the form or the input controls to convert or supply the correct values.

Why does the form take many seconds to load in Power Apps?

Long load times may be caused by large SharePoint lists, complex lookups, many columns, or heavy OnVisible formulas that fetch data. Reduce initial data calls, use delegation-friendly queries, and limit list columns retrieved. Consider custom pages or optimizing connectors and ensure Power Platform and connector endpoints are healthy. Monitor network latency with Power Apps Monitor to isolate slow API responses.

What should I do when a custom SharePoint form in PowerApps shows a requested operation is invalid?

This error often stems from invalid data being sent (wrong data type, missing lookup ID) or outdated connectors. Check that the form in PowerApps maps fields to the correct SharePoint list using the SharePoint list form settings, adjust the form control DataSource, and retest. If the issue persists, inspect Microsoft Q&A and Power Platform Community Forum thread for similar issue reports and any known service incidents.

How do I use OnSuccess and OnFailure to notify the user after submit?

Configure the Edit Form’s OnSuccess property to run Notify(“Saved successfully”, NotificationType.Success) and reset the form or navigate. Use OnFailure to Notify(“Save failed: ” & First(Errors(DataSource)).Message, NotificationType.Error) and log details for debugging. This ensures users get immediate feedback and you capture errors that occur for troubleshooting.

Can security updates or tenant settings cause forms to fail?

Yes. Admins may enforce conditional access, app restrictions, or security updates that change connector behavior. Confirm Microsoft 365 admin settings, connector permissions, and whether the API used by the connector is blocked. If corporate policies changed, coordinate with admins or technical support to ensure apps have required permissions.

What are simple ways to fix common Power Apps form problems?

Simple fixes include: verify form DataSource and item binding, ensure Submit button OnSelect calls SubmitForm, match sharepoint list column types, populate required fields, use Power FX to validate inputs before submitting, and clear or reset input controls on success. Leverage Power Apps Monitor and community resources for further solutions to common issues.

How do I handle errors from lookups, people pickers, or complex columns?

For lookup and people picker fields, send the ID and not just the display value. For example, for a lookup field, patch {LookupField: {Id: value}}. Use the appropriate data card value property and ensure the form control is bound correctly. If an error occurs, Power Apps Monitor and the Errors function can reveal the missing or invalid field data.

Why does a form work in preview but fail when published or used by others?

Differences often come from permission levels, different data contexts, or hard-coded user IDs. Check that all users have access to the SharePoint site and list, connectors are shared correctly, and any environment variables or custom connectors are available to all. Also confirm delegation and data row limits aren’t causing silent failures for other users.

How can I debug Power Fx formulas that cause form submission problems?

Use formulas in labels or temporary controls to show intermediate values (e.g., show the value bound to a field). Validate boolean expressions (true or false) and ensure OnSelect logic doesn’t short-circuit SubmitForm. The Trace capability in Power Apps Monitor helps identify which formula or control produced the error. Break complex formulas into smaller steps and test each.

What role does Power Automate play when forms fail and how to troubleshoot it?

If a Submit triggers a Power Automate flow, check the flow run history and returned errors. Common issues include schema mismatches, invalid JSON, or connector authentication. Ensure the flow expects the same list columns and field names (list using correct schema) and that the app passes required values. Fix the flow or map fields correctly to resolve the failure.

When should I contact technical support or post on Microsoft Q&A / Power Platform Community Forum thread?

Contact technical support if you suspect platform-level outages, security updates, or complex API errors you cannot resolve. For configuration, formula, or design issues, search Microsoft Q&A or post a detailed Power Platform Community Forum thread including Monitor traces, error messages, and steps to reproduce. Community members often provide solutions to common or similar issue scenarios quicker.

How can I prevent data entry errors from causing failed submissions?

Add validation using Power FX on Text input and input control properties, use Regex or IsMatch to validate formats, and disable the Submit button until required fields are valid. Provide clear error messages via Notify or label controls. This reduces errors that occur from incorrect user input and improves data quality in SharePoint list forms.

Why do errors show “value larger than allowed” or “invalid field value” and how to fix?

These errors occur when the data sent doesn’t comply with SharePoint column constraints (e.g., text length, number range, choice values). Adjust the Text property limitations, trim inputs, or change the SharePoint list schema if necessary. Ensure Power FX calculations produce valid values before submitting.

Can connector throttling or API limits cause intermittent form failures?

Yes. High frequency calls can hit API limits or throttling on SharePoint or other connectors. Batch operations where possible, reduce unnecessary calls on app start, and implement retry logic. Monitor response codes in Power Apps Monitor for 429 or 503 errors and consult connector documentation for limits.

What do I do when the form control keeps resetting or losing input values?

Check that Default and DefaultSelectedItems properties map correctly and that any Reset functions or OnVisible code aren’t unintentionally clearing controls. If the form is reloaded due to navigation or data refresh, preserve unsaved changes using a context variable or save drafts to a temporary list. Ensure Save button logic completes (OnSuccess) before navigating away.

How do I ensure apps to ensure compliance and reduce form failures?

Adopt best practices: centralize data access using connectors with proper permissions, keep lists lean with necessary columns only, implement validation and error handling using Power FX, test across user roles, and monitor apps with Power Apps Monitor. Regularly review security updates and coordinate with admins to prevent unexpected permission changes.

🚀 Want to be part of m365.fm?

Then stop just listening… and start showing up.

👉 Connect with me on LinkedIn and let’s make something happen:

• 🎙️ Be a podcast guest and share your story
• 🎧 Host your own episode (yes, seriously)
• 💡 Pitch topics the community actually wants to hear
• 🌍 Build your personal brand in the Microsoft 365 space

This isn’t just a podcast — it’s a platform for people who take action.

🔥 Most people wait. The best ones don’t.

👉 Connect with me on LinkedIn and send me a message:
“I want in”

Let’s build something awesome 👊